Australia Consumer Data Right - Banking (CDR)
Information Security (Schedule 2)

Australia Consumer Data Right - Banking (CDR) AUCDR-IS-4: Formal vulnerability management program

Implement a formal vulnerability management program to identify, track and remediate vulnerabilities in the CDR data environment in a timely manner, including security patching and secure coding.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 75 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 7 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process
  • CIS-7.2 Establish and Maintain a Remediation Process
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-7.4 Perform Automated Application Patch Management
  • CIS-7.7 Remediate Detected Vulnerabilities

FedRAMP High · 6 controls

  • CA-5 Plan of Action and Milestones
  • RA-5 Vulnerability Monitoring and Scanning
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SI-2 Flaw Remediation

FedRAMP Moderate · 6 controls

  • CA-5 Plan of Action and Milestones
  • RA-5 Vulnerability Monitoring and Scanning
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SI-2 Flaw Remediation

C5 (Germany) · 4 controls

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities
  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

NIST SP 800-53 Rev 5 · 4 controls

  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • PV-5 Perform vulnerability assessments

CMMC 2.0 · 3 controls

HIPAA Security Rule · 3 controls

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.8 Management of technical vulnerabilities
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

PCI DSS 4.0 · 3 controls

  • 11.3.1 11.3.1 Quarterly internal vulnerability scans
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 6.3.3 6.3.3 Timely installation of security patches

ACSC Essential Eight · 2 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)

ISO 27701:2019 · 2 controls

  • 6.11.2 Security in development and support processes
  • 6.9.6 Technical vulnerability management

NIST SP 800-171 Rev 3 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • CBPR-PR-30 Specific proportional safeguards in place

GDPR · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Information Security (Schedule 2)

You are reading one control. How much of Australia Consumer Data Right - Banking (CDR) have you already done?

Australia Consumer Data Right - Banking (CDR) AUCDR-IS-4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Australia Consumer Data Right - Banking (CDR) your existing evidence covers. Hold ISO 27701:2019 and 16 of 24 Australia Consumer Data Right - Banking (CDR) controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the ISO 27701:2019 pair alone.

Query this from an agent

The graph holds this control, the 75 it maps to, and the evidence behind each claim, over MCP and REST.