Weekly maintenance tasks that must be performed for PCI DSS 4.0

1. Network Monitoring and Security

  • Access firewall and router management interfaces.
  • Locate logs related to access attempts.
  • Filter for unauthorized access entries.
  • Document any suspicious activities.
  • Report findings to the security team.
  • Identify all network devices requiring updates.
  • Check vendor websites for the latest patches.
  • Schedule updates during maintenance windows.
  • Test updates in a staging environment.
  • Apply updates and monitor for issues.
  • Access the IDS/IPS management console.
  • Check for any alerts or notifications.
  • Run diagnostic tests to ensure functionality.
  • Review configuration settings for accuracy.
  • Document operational status and any issues.
  • Use network scanning tools to initiate scans.
  • Define parameters for unauthorized devices.
  • Review scan results for unexpected devices.
  • Investigate unauthorized devices promptly.
  • Update asset inventory accordingly.
  • Utilize network monitoring tools for traffic analysis.
  • Establish baseline traffic patterns.
  • Look for deviations from established norms.
  • Investigate any anomalies in detail.
  • Report findings and suggest actions.
  • Access the firewall configuration interface.
  • Compile a list of currently open ports/protocols.
  • Cross-reference with business needs.
  • Remove unnecessary rules and document changes.
  • Test firewall functionality post-update.
  • Enable logging for remote access connections.
  • Regularly review connection logs for anomalies.
  • Identify and investigate unfamiliar IP addresses.
  • Ensure proper user authentication methods are used.
  • Report unauthorized access attempts immediately.
  • Verify wireless network settings.
  • Ensure WPA3 or higher is used for encryption.
  • Check authentication protocols for compliance.
  • Conduct periodic security assessments.
  • Update settings as necessary to enhance security.
  • Identify sensitive data and network segments.
  • Perform access control tests on segments.
  • Verify that unauthorized access is effectively blocked.
  • Document test results and any vulnerabilities found.
  • Adjust segmentation policies based on findings.
  • Draft or update network access control policy.
  • Specify roles and permissions for devices.
  • Ensure policies align with compliance requirements.
  • Communicate policies to all stakeholders.
  • Review policies regularly for relevance.
  • Schedule vulnerability assessments quarterly.
  • Utilize recognized vulnerability scanning tools.
  • Review assessment reports for findings.
  • Prioritize vulnerabilities based on severity.
  • Develop remediation plans for identified risks.
  • Access IDS/IPS alert logs.
  • Categorize alerts by severity and type.
  • Investigate high-severity alerts promptly.
  • Document investigation findings and actions taken.
  • Update incident response procedures as necessary.
  • Create a standardized incident report template.
  • Include all relevant details in reports.
  • Distribute reports to security teams and management.
  • Follow up on incident response actions.
  • Store reports for future reference and compliance.
  • Review configurations of all monitoring tools.
  • Test functionalities to verify proper operation.
  • Update configurations based on network changes.
  • Document configurations and any issues.
  • Train staff on tool usage and best practices.
  • Schedule architecture reviews bi-annually.
  • Refer to applicable security standards for compliance.
  • Identify areas of non-compliance or risk.
  • Document findings and recommend improvements.
  • Communicate findings to relevant stakeholders.

2. Vulnerability Management

  • Schedule scans using automated tools.
  • Include all systems within the CDE.
  • Generate reports post-scan for analysis.
  • Ensure scans cover all relevant network segments.
  • Analyze scan reports for vulnerabilities.
  • Assign remediation tasks to appropriate personnel.
  • Set deadlines based on risk levels.
  • Verify remediation completion and effectiveness.
  • Record all vulnerabilities and remediation steps.
  • Ensure documentation reflects current state.
  • Review and update documentation regularly.
  • Distribute updated documentation to relevant stakeholders.
  • Create a detailed list of all hardware and software assets.
  • Regularly update the inventory to reflect changes.
  • Ensure all assets are categorized based on their role within the CDE.
  • Use automated tools for inventory management where possible.
  • Subscribe to reliable threat intelligence services.
  • Regularly review and analyze threat feeds for relevant vulnerabilities.
  • Cross-reference identified vulnerabilities with the CDE asset inventory.
  • Adjust security measures based on threat intelligence findings.
  • Engage qualified external or internal testers.
  • Define the scope of the penetration test clearly.
  • Document findings and prioritize identified vulnerabilities.
  • Schedule follow-up testing to validate remediation efforts.
  • Develop a risk assessment framework to evaluate vulnerabilities.
  • Assign severity levels to each vulnerability based on impact and exploitability.
  • Create a remediation timeline based on prioritization.
  • Review prioritization criteria regularly to adapt to new threats.
  • Maintain a list of all third-party software and services.
  • Conduct regular security assessments on third-party solutions.
  • Require third-party vendors to provide compliance documentation.
  • Monitor third parties for any reported vulnerabilities.
  • Set up automated systems for detecting critical vulnerabilities.
  • Customize alert thresholds based on organizational risk tolerance.
  • Ensure alerts are sent to relevant personnel for quick action.
  • Regularly review alert configurations for effectiveness.
  • Create a review schedule, at least annually.
  • Involve key stakeholders in the review process.
  • Document changes and improvements made to processes.
  • Use findings to update training and awareness programs.
  • Develop training materials focused on vulnerability management.
  • Schedule regular training sessions for relevant staff.
  • Incorporate secure coding practices into development training.
  • Evaluate training effectiveness through assessments and feedback.
  • Create a remediation tracking system or database.
  • Log details for each vulnerability, including status and actions taken.
  • Assign responsible parties for each remediation effort.
  • Review and update documentation regularly.
  • Develop workflows that link vulnerability management with incident response.
  • Conduct joint training sessions for both teams.
  • Document procedures for escalating vulnerabilities that are exploited.
  • Review integration effectiveness after incidents.

3. Access Control and Authentication

  • Access logs should be collected from all systems.
  • Analyze logs for unusual patterns or entries.
  • Investigate any flagged activity immediately.
  • Document findings and take necessary actions.
  • Review current access rights for each user.
  • Compare rights against job responsibilities.
  • Adjust access levels to adhere to least privilege principle.
  • Document any changes made during the review.
  • Identify users who have left the organization.
  • Revoke access immediately upon termination.
  • Update access logs to reflect changes.
  • Communicate changes to relevant teams.
  • Schedule periodic reviews of user roles.
  • Confirm that permissions match job duties.
  • Adjust roles as necessary based on changes.
  • Document review outcomes and actions taken.
  • Identify all sensitive systems requiring MFA.
  • Configure MFA settings for each system.
  • Communicate MFA requirements to users.
  • Monitor for compliance and address issues.
  • Ensure logging is enabled on critical systems.
  • Define log retention periods based on compliance.
  • Regularly review logs for access patterns.
  • Securely store logs to prevent tampering.
  • Establish password complexity requirements.
  • Implement regular password change intervals.
  • Communicate password guidelines to users.
  • Monitor compliance with password policies.
  • Develop training materials covering access security.
  • Schedule regular training sessions for staff.
  • Include phishing and credential management topics.
  • Evaluate training effectiveness through feedback.
  • Define criteria for granting temporary access.
  • Document requests and approvals for access.
  • Log all temporary access grants and usage.
  • Review temporary access regularly for necessity.
  • Schedule regular policy review sessions.
  • Incorporate feedback from stakeholders.
  • Update policies to reflect regulatory changes.
  • Communicate updates to all staff.
  • Define the number of allowed failed attempts.
  • Configure lockout settings in the system.
  • Communicate lockout policy to users.
  • Monitor accounts for lockout incidents.
  • Identify all remote access methods used.
  • Require VPN for remote access to sensitive systems.
  • Log all remote access activities.
  • Regularly review remote access logs for anomalies.
  • Track all changes made to access policies.
  • Create a summary of policy updates.
  • Distribute updates to all relevant personnel.
  • Gather feedback on the communicated changes.

4. Data Protection

5. Incident Response

  • Gather incident reports from the past week.
  • Analyze the incidents for severity and impact.
  • Document the timeline and response actions taken.
  • Identify any gaps in the response process.
  • Create a summary report for future reference.
  • Select a realistic incident scenario for the exercise.
  • Gather relevant personnel and outline the exercise objectives.
  • Facilitate discussions on response actions and decision-making.
  • Collect feedback on the incident response plan's effectiveness.
  • Document insights and areas for improvement.
  • Review documentation from recent incidents.
  • Identify changes needed in procedures or policies.
  • Incorporate feedback from tabletop exercises.
  • Revise the incident response plan accordingly.
  • Distribute the updated plan to all relevant personnel.
  • Organize training sessions for all relevant personnel.
  • Review key components of the updated incident response plan.
  • Clarify specific roles and responsibilities during incidents.
  • Conduct quizzes or simulations to reinforce learning.
  • Document attendance and completion of training.
  • Identify assets that need protection.
  • Evaluate potential threats and vulnerabilities for each asset.
  • Analyze the impact of identified risks on operations.
  • Prioritize risks based on likelihood and impact.
  • Document findings and recommend mitigation strategies.
  • Assess current communication protocols for clarity and efficiency.
  • Test communication channels with a mock incident.
  • Evaluate response times and information accuracy.
  • Make necessary adjustments to improve communication flow.
  • Document the results of the communication test.
  • Review the configuration settings of detection tools.
  • Test tools against known threats to verify alerts.
  • Ensure monitoring systems cover all critical areas.
  • Document the performance of detection tools.
  • Adjust settings based on test results and findings.
  • Gather all relevant data and logs from the incident.
  • Identify the root cause and contributing factors.
  • Assess the impact on systems and data.
  • Document all findings in a forensic report.
  • Recommend actions to prevent recurrence.
  • Compile a list of all relevant stakeholders.
  • Verify the accuracy of contact details.
  • Update any changes in personnel or roles.
  • Ensure contact information is accessible to all team members.
  • Document the updated contact list.
  • Identify key performance indicators (KPIs) for incident response.
  • Set benchmarks for response times and outcomes.
  • Collect data on incidents and responses regularly.
  • Analyze trends and improvements over time.
  • Report metrics to management for review.
  • Create a schedule for follow-up meetings.
  • Review the status of corrective actions taken.
  • Assess the effectiveness of implemented changes.
  • Document outcomes of follow-up discussions.
  • Adjust follow-up frequency based on incident severity.
  • Establish a secure storage solution for documentation.
  • Organize documents by incident type and date.
  • Ensure access controls are in place.
  • Regularly review and update stored documents.
  • Create a backup strategy for critical documentation.
  • Identify third-party service providers relevant to incident response.
  • Schedule meetings to discuss their incident response plans.
  • Compare their policies against your organization's requirements.
  • Document any discrepancies and areas for improvement.
  • Establish a follow-up plan to ensure alignment.

6. Security Training and Awareness

7. Documentation and Reporting

  • Gather data on all completed tasks.
  • Include dates, times, and personnel involved.
  • Summarize key findings and outcomes.
  • Format the report for clarity and readability.
  • Distribute to relevant stakeholders.
  • Record the date and time of each issue.
  • Describe the nature of the issue clearly.
  • Detail the steps taken to resolve the issue.
  • Note any follow-up actions required.
  • Ensure documentation is accessible for future reference.
  • Identify the changes in compliance requirements.
  • Assess current policies and procedures against these changes.
  • Update documentation to align with new requirements.
  • Circulate revised documents for team review.
  • Obtain approval from necessary stakeholders.
  • Record the date and nature of each change.
  • Include the system or application affected.
  • Document who made the change and why.
  • Ensure logs are kept in a secure location.
  • Review logs regularly for discrepancies.
  • Summarize findings from the assessment/audit.
  • Include any vulnerabilities identified.
  • Detail recommendations for remediation.
  • Assign responsibilities for addressing findings.
  • Distribute results to relevant teams.
  • List all updates and patches applied.
  • Include the date and system/application affected.
  • Document the purpose of each update.
  • Track any issues arising from updates.
  • Verify successful installation of patches.
  • Log date and time of each access request.
  • Include details of the individual requesting access.
  • Document the approval process and outcomes.
  • Update access control lists accordingly.
  • Review access logs for unauthorized changes.
  • Document the timeline of the incident.
  • Detail the nature and impact of the breach.
  • Outline the response actions taken.
  • Include lessons learned and follow-up actions.
  • Share summaries with relevant stakeholders.
  • Create a feedback form for team members.
  • Schedule a meeting to discuss feedback.
  • Encourage open and honest responses.
  • Analyze feedback for common themes.
  • Document suggestions for future improvements.
  • Identify a secure storage solution.
  • Organize documents for easy access.
  • Set permissions for authorized personnel only.
  • Regularly back up stored documentation.
  • Review access logs to ensure compliance.
  • Cross-check details against original sources.
  • Ensure all necessary information is included.
  • Validate data for accuracy.
  • Seek peer review for additional insights.
  • Make necessary revisions before finalizing.
  • Establish a review schedule (e.g., quarterly).
  • Assign responsibilities for each review.
  • Document changes made during reviews.
  • Notify team members of upcoming reviews.
  • Update documentation as needed post-review.
  • List all documents required for compliance.
  • Organize checklist by category or type.
  • Ensure clarity in item descriptions.
  • Distribute checklist to relevant team members.
  • Update checklist as compliance requirements change.

8. Third-party Service Provider Management

  • Assess the provider's security policies and procedures.
  • Evaluate past security incidents and breaches.
  • Check for industry certifications and compliance reports.
  • Review their incident response and risk management frameworks.
  • Include explicit requirements for PCI DSS compliance.
  • Specify responsibilities for data protection and incident reporting.
  • Define consequences for non-compliance.
  • Review contracts annually for updates or changes in regulations.
  • Request compliance reports on a scheduled basis.
  • Verify the authenticity of submitted compliance documentation.
  • Ensure reports include detailed findings and remediation actions.
  • Track deadlines for ongoing compliance reporting.
  • Identify and document the services provided by each vendor.
  • Assess potential risks associated with their access to data.
  • Evaluate potential impacts on cardholder data confidentiality.
  • Update risk assessments annually or after significant changes.
  • Review the provider's security architecture and controls.
  • Test security measures for effectiveness and compliance.
  • Assess alignment with PCI DSS requirements and best practices.
  • Document findings and follow up on any deficiencies.
  • Request AoC or RoC from each provider annually.
  • Verify that documents are current and signed by a qualified assessor.
  • Review compliance documentation for accuracy and completeness.
  • Store copies securely for future reference.
  • Establish a monitoring system for security alerts.
  • Review incident reports and responses from providers.
  • Communicate with providers about any incidents affecting data.
  • Assess the impact of incidents on your organization’s data.
  • Schedule regular reviews of contracts and compliance status.
  • Document any changes made to agreements.
  • Ensure updates reflect changes in PCI DSS requirements.
  • Communicate changes to relevant stakeholders.
  • Request documentation of the provider's incident response plan.
  • Review alignment with your organization’s incident response procedures.
  • Conduct joint incident response drills if possible.
  • Update your procedures based on findings.
  • Develop training materials on PCI DSS requirements.
  • Schedule regular training sessions for provider personnel.
  • Assess training effectiveness through quizzes or feedback.
  • Document attendance and training completion.
  • Define procedures for access termination in contracts.
  • Notify providers of the termination process in advance.
  • Ensure all access credentials are revoked immediately.
  • Document the termination process and outcomes.
  • Set a regular schedule for compliance reviews.
  • Document findings and follow up on outstanding issues.
  • Adjust monitoring frequency based on risk levels.
  • Communicate results with relevant stakeholders.
  • Create and update a centralized inventory database.
  • Include details such as service descriptions and compliance status.
  • Review the inventory regularly for accuracy.
  • Ensure inventory is accessible to relevant personnel.

9. System Configuration and Management

  • Review current configurations against PCI DSS requirements.
  • Identify any discrepancies or non-compliant settings.
  • Document compliance status and any required changes.
  • Schedule remediation for any non-compliant configurations.
  • Maintain records of compliance reviews for auditing.
  • Verify that all changes are logged in the change management system.
  • Ensure approval workflows are followed for all modifications.
  • Document the rationale and impact of changes made.
  • Maintain historical records of changes for accountability.
  • Review change logs for compliance with policies regularly.
  • Check the status of logging services on all systems.
  • Ensure logs are generated as per compliance requirements.
  • Verify log retention settings align with organizational policies.
  • Test log integrity and accessibility for review.
  • Document any issues found and remediate promptly.
  • Schedule weekly configuration reviews.
  • Utilize automated tools for compliance checks.
  • Document findings and actions taken.
  • Involve relevant stakeholders in the review process.
  • Deploy security controls as per design.
  • Conduct tests to validate effectiveness.
  • Document test results and any issues.
  • Adjust controls based on testing feedback.
  • Compare current guidelines against industry benchmarks.
  • Update guidelines to reflect new threats.
  • Distribute updated guidelines to relevant teams.
  • Train staff on new hardening practices.
  • Identify all systems with default settings.
  • Change all default passwords to strong alternatives.
  • Disable unused default services and accounts.
  • Document changes for future audits.
  • Schedule regular automated scans.
  • Review scan results for discrepancies.
  • Remediate any identified deviations promptly.
  • Maintain records of scan results.
  • Log all exceptions with detailed justification.
  • Obtain management approval for each exception.
  • Review exceptions periodically for relevance.
  • Document any changes to exception status.
  • Establish a patch management schedule.
  • Track all patches applied with a centralized system.
  • Review patch status regularly for compliance.
  • Communicate with teams about upcoming patches.
  • Check all systems for anti-malware software.
  • Ensure regular updates for signature files.
  • Conduct regular scans for malware detection.
  • Document the status of anti-malware controls.
  • Schedule assessments at regular intervals.
  • Use a standardized assessment framework.
  • Document findings and recommendations.
  • Follow up on remediation actions taken.
  • Create a review schedule for third-party services.
  • Evaluate security practices of third-party vendors.
  • Document findings and required actions.
  • Communicate results to relevant stakeholders.
  • Implement secure coding guidelines.
  • Conduct regular code reviews with peer feedback.
  • Use automated tools for vulnerability assessment.
  • Document any identified vulnerabilities and fixes.
  • Create and update a comprehensive inventory list.
  • Include software versions and patch levels.
  • Review inventory regularly for accuracy.
  • Utilize inventory for compliance audits.

10. Review of Policies and Procedures

Related Checklists