What does a cyber application ask about patching and vulnerabilities?
Patching appears on 68 application questions across 32 of the 48 carrier forms. Each question below is verbatim, with the control it reaches and the evidence to have on file. This page never says what a carrier will accept: that is the carrier's underwriting decision.
The questions, verbatim and mapped
Application question How often do you patch your operating sytems?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question How often do you conduct vulnerability scanning of your network perimeter?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Do you, or an outsourced service provider on your behalf, actively manage and install critical patches across your internet-facing systems?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Regular updating and patching of critical systems and software in a timely manner?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Are there any end-of-life or end-of-support software in use?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question When did the Applicant last have a comprehensive (i.e. inclusive of vulnerability scanning and penetration testing) network security assessment completed?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question What is the Applicant's Critical Patching Target?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant maintain a Normal Vulnerability Management patching target within 30 days?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant have any End-of-Life software or systems present in its environment?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question In response to any of these matters, has the Applicant commenced or completed any change to its network and information security and handling practices, or other changes, to remediate the effects of the matter or remove a vulnerability that gave rise to the matter?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question A process in place to regularly download, test, and install patches If Yes, is this process automated?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question If Yes, are critical patches installed within 30 days of release?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Annual penetration testing If Yes, is such testing conducted by a third party service provider?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you conduct penetration testing of your network at least annually?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question How often does the organization apply updates to critical IT-systems and applications ("security patching"?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the applicant track compliance for deploying critical patches?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the applicant have a policy (to enforce) when patches must be deployed?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question If yes, what is the timeframe critical patches must be deployed?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the applicant have any end-of-life (EOL) software or applications currently running on the network?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question If yes, how is that patched and managed?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Are backups tested for vulnerabilities/malware prior to restoration?
- ISO 27001:2022 A.8.13: Information backup. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- SOC 2 A1.3: Testing recovery plan procedures. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- NIST CSF 2.0 PR.DS-11: Backups of data are created, protected, maintained, and tested. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.2: Perform Automated Backups. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- CIS Controls v8 11.4: Establish and Maintain an Isolated Instance of Recovery Data. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the backup configuration and schedule, and the restore-test record with its date; the report of the last successful restore, or the notes of a restore drill.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the applicant conduct full vulnerability scans across the entirety of its network?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Do you check for security patches to your systems at least weekly and implement them within 30 days?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you have up-to-date versions of system security agent software (including malware, antivirus, and firewall protection) and reasonably up-to-date (within 30 days) security patches and virus definitions?
- ISO 27001:2022 A.8.7: Protection against malware. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- NIST CSF 2.0 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question How frequently do you install critical and high severity patches across your enterprise?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you have any end of life or end of support software?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you use a vulnerability management tool?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question If "Yes", complete the following: (1) Provide the name of your provider: (2) What is your patching cadence?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Vulnerability Assessment and Remediation Does the Applicant have a formal process in place to detect software/application vulnerabilities and automatically push critical updates and patches to all computing resources?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question If "Yes", is the length of time required for the deployment of critical updates and patches less than or equal to 2 weeks?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you regularly conduct vulnerability scanning across your internal and external-facing assets?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Do you ensure that any acquired applications/functions and code is free from known vulnerabilities?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC8.1: Managing changes to procedures, software, data and infrastructure. Evidence to have on file: the secure-development standard and the checks a change goes through before release; a sample of a code review or security test for a recent release.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question What is the capability to deploy the highest priority patches outside the regular periodic patching processes? (for example, in the case of an in-the-wild exploitation of software for which an out-of-band patch is available)?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.3: Role-based access, least privilege and segregation of duties. Evidence to have on file: the documented callback or out-of-band procedure for verifying a change to supplier or payee bank details, naming who checks and how; a contact channel verified before the request was made, held independently of the message that asked for the change.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Are regular vulnerability scans of externally exposed environments being performed?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Do you install critical and high severity patches across your enterprise within one month?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Is there a patch management process in place? if yes, what is the timeframe for implementing patches following identification?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you or any third parties conduct any penetration & vulnerability testing? If yes, have any major findings been remediated? If no, please explain.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the applicant Conduct Vulnerabilty assessments / penetration tests of its network at least annually?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Operate a patch management strategy?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question (b) i) vendors automatic patching (updates) enabled for all software and operating systems OR ii) patch cycles tested and deployed against large or critical sets of servers and desktops?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant have a formal program in place to conduct third-party penetration testing or audit network security controls annually? (i) If YES, are test/audit findings tracked, remediated and retested?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant currently have penetration tests in place?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Applicant currently carry out vulnerability scans?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Applicant enforce a software update process, including patches and anti-virus software?
- ISO 27001:2022 A.8.7: Protection against malware. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- NIST CSF 2.0 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Applicant use any end-of-life or unsupported software? If Yes, how are they separated from the rest of the Applicant's network?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question What process or procedure is in place to ensure outsourced service providers have addressed the Log4j vulnerability?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you check for security patches to your systems at least weekly and implement them within 30 days?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you install critical patches within 30 days of release?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Please confirm how quickly critical patches are carried out.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you conduct vulnerability assessments / penetration tests of your network at least annually?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Operate a patch management strategy?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question How often are operating system updates and patches installed?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you have established processes for rapidly applying critical security patches across servers, laptops, desktops, and managed mobile devices?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you deploy non-critical patches across servers, laptops, desktops, and managed mobile devices within 30 days, and critical patches (CVSS v3 score of 7 or above) within 14 days frequently?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.1: Logical access security over protected information assets. Evidence to have on file: the mobile-device management configuration and the devices it enrols; a report of enrolled devices and their compliance state.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you have protocols for replacement of end-of-life system/network equipment?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you update and patch critical IT-systems and applications on at least a monthly basis?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you (yourself or by engaging an outside vendor) regularly scan critical systems for security vulnerabilities? These scans may include security and penetration testing.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Applicant run vulnerability scans or penetration tests against all parts of the Applicant's network?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the applicant proactively address system vulnerabilities, including regular updates to anti-virus/malware protection and critical security patches?
- ISO 27001:2022 A.8.7: Protection against malware. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.1: User end point devices. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC6.8: Preventing and detecting unauthorised or malicious software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-05: Installation and execution of unauthorized software are prevented. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- NIST CSF 2.0 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 5: Protect All Systems and Networks from Malicious Software. Evidence to have on file: the endpoint-protection or EDR console report showing coverage and the last agent update; a sample of a detection or quarantine event and its handling.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Has the applicant had a vulnerability assessment, penetration test, or other network security assessment performed in the last 12 months?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC6.6: Protection against threats from outside the system boundary. Evidence to have on file: the firewall or network-segmentation configuration for the boundary the question names; a sample of the rule set, with the business reason for each open path.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Applicant have a written security patch management process implemented?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Is a vulnerability scan or penetration test performed on all Internet-facing applications and systems before they go into production and at least quarterly thereafter?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- CIS Controls v8 7.1: Establish and Maintain a Vulnerability Management Process. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the vulnerability-scanning schedule, and the scope it covers (the perimeter or the assets the question names); the dated scan results from the most recent run, with the findings it raised.
Application question Does the Proposer enforce software update process with the installation of software patches?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Are critical patches installed within 30 days of release?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Does the Proposer enforce software update process with the installation of software patches (third party section)?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Have you implemented a critical security patch management process for your IT systems?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Do you install all security patches (all vendors e.g. Microsoft) within 30 days of release?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC9.2: Assessing and managing vendor and business partner risk. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- APRA CPS 234 para 16: Assess the security capability of related and third parties. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 22: Evaluate the design of third-party controls. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- APRA CPS 234 para 28: Assess reliance on third-party control testing. Evidence to have on file: the supplier or vendor register, with the security terms each is held to; a sample of a completed supplier due-diligence review.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Application question Are any business-critical functions carried out on end-of-life/legacy systems where security patches are no longer available?
- ISO 27001:2022 A.8.8: Management of technical vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.19: Installation of software on operational systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ISO 27001:2022 A.8.29: Security testing in development and acceptance. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- SOC 2 CC7.1: Detecting configuration changes and new vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- NIST CSF 2.0 PR.PS-02: Software is maintained, replaced, and removed commensurate with risk. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHAPP: Patch applications. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- ACSC Essential Eight PATCHOS: Patch operating systems. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.3: Perform Automated Operating System Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.4: Perform Automated Application Patch Management. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- CIS Controls v8 7.7: Remediate Detected Vulnerabilities. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 6: Develop and Maintain Secure Systems and Software. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
- PCI DSS 4.0 Requirement 11: Test Security of Systems and Networks Regularly. Evidence to have on file: the patch or vulnerability-management policy with the remediation windows it sets; a report of outstanding critical patches against the stated window.
Frequently asked questions
How many carriers ask about patching?
32 of the 48 carrier forms ask about patching, on 68 questions.
What time frame do the forms ask about?
The windows differ by form (for example thirty days for non-critical and fourteen for critical). The questions on this page state the window each form names.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.