Vulnerability scan export
The shortest fixed clock in these texts is 2,190 hours (every three months), set by PCI DSS 11.3.1. Paste one job that feeds this consumer, for example vuln_scan_export, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: vuln, vulnerability, scan export, scanner, scan report, asv scan, vulnerability scan.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | 2,190h | PCI DSS 11.3.1 Quarterly internal vulnerability scansat least once every three months |
| 2,190h | PCI DSS 11.3.2 Quarterly ASV external vulnerability scansat least once every three months | |
| SP 800-53 | no clock | SP 800-53 RA-5 Vulnerability monitoring and scanninga defined frequency |
| ISO 27001 | no clock | ISO 27001 8.8 Management of technical vulnerabilities |
| NIS2 | no clock | NIS2 Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure |
Questions this page answers
How often does PCI DSS v4.0 require vulnerability scan export?
Every three months (2,190 hours): PCI DSS 11.3.1, Quarterly internal vulnerability scans. Every three months (2,190 hours): PCI DSS 11.3.2, Quarterly ASV external vulnerability scans. Internal vulnerability scans must be run at least every three months. All vulnerabilities ranked high-risk or critical under the entity's risk rankings from Requirement 6.3.1 must be resolved, and rescans must be run to confirm that every such high-risk and critical finding is fixed. The scanning tool must be kept current with the latest vulnerability information, and the people running scans must be qualified and organizationally independent of what they scan. Guidance (good practice): several scan reports may be combined to show full coverage within the three-month cycle, and scanning more often than quarterly is recommended where the environment warrants it. Applicability: a QSA or ASV is not needed for internal scans; qualified internal staff reasonably independent of the scanned components (for example, not the administrator of that network) may run them, or a specialist scanning firm may be used. Objective under the customized approach: automated tools that detect vulnerabilities inside the network periodically verify the security state of every system component, and findings are assessed and fixed using a formal risk assessment framework. External vulnerability scans must meet these conditions: they run at least every three months; an Approved Scanning Vendor (ASV) listed by the PCI SSC performs them; with vulnerabilities resolved and the ASV Program Guide conditions for a passing scan met; and with rescans run as needed to confirm resolution under those passing-scan conditions. Applicability: for the first PCI DSS assessment against this requirement, four passing scans within 12 months are not required if the assessor confirms (1) the latest scan passed, (2) documented policies and procedures mandate quarterly scanning, meaning at least every three months, plus (3) rescans show the reported vulnerabilities were fixed. From the second year onward, a passing scan is needed for every three-month period. Details of the target environment (load balancers, third parties, ISPs, configurations, protocols, scan interference) are for the ASV and the scan customer to settle between them, with the ASV Program Guide describing scan customer responsibilities. Customized approach objective: not eligible for the customized approach.
How often does NIST SP 800-53 Rev 5 require vulnerability scan export?
The text of SP 800-53 RA-5 (Vulnerability monitoring and scanning) sets no fixed period: a defined frequency. Requires vulnerability monitoring and scanning of the system and hosted applications at a defined frequency or randomly by a defined process and when new relevant vulnerabilities are reported, using tools and techniques that support standardised enumeration, checklists and impact measurement, with results analysed, remediation within defined response times by risk, results shared with defined personnel, and privileged scanning access where required.
How often does ISO/IEC 27001:2022 require vulnerability scan export?
The text of ISO 27001 8.8 (Management of technical vulnerabilities) sets no fixed period: no period set by the text. Obtain vulnerability information, evaluate exposure, and take appropriate remediation.
How often does NIS2 Directive require vulnerability scan export?
The text of NIS2 Art.21.2.e (Security in acquisition, development and maintenance, including vulnerability handling and disclosure) sets no fixed period: no period set by the text. Two duties travel together in this point. The first is that security is built into how systems are acquired, developed and maintained: security requirements set before purchase or build, secure development practice, change control, and maintenance that does not quietly reintroduce weakness. The second is vulnerability handling and disclosure, meaning the entity can receive a vulnerability report about its own products or systems, triage it, fix it on a timescale that reflects severity, and handle disclosure. A published route for a finder to reach the entity is the part most often missing, and its absence is visible from outside. Note that the coordinator role and the European vulnerability database in Article 12 belong to the CSIRTs and ENISA; what binds the entity is its own handling and disclosure capability.
What does the register ask the owner of a vulnerability scan export job?
Who owns the high and critical findings in each export, and does the re-scan job exist?
The clauses in full
Internal vulnerability scans must be run at least every three months. All vulnerabilities ranked high-risk or critical under the entity's risk rankings from Requirement 6.3.1 must be resolved, and rescans must be run to confirm that every such high-risk and critical finding is fixed. The scanning tool must be kept current with the latest vulnerability information, and the people running scans must be qualified and organizationally independent of what they scan. Guidance (good practice): several scan reports may be combined to show full coverage within the three-month cycle, and scanning more often than quarterly is recommended where the environment warrants it. Applicability: a QSA or ASV is not needed for internal scans; qualified internal staff reasonably independent of the scanned components (for example, not the administrator of that network) may run them, or a specialist scanning firm may be used. Objective under the customized approach: automated tools that detect vulnerabilities inside the network periodically verify the security state of every system component, and findings are assessed and fixed using a formal risk assessment framework.
What an assessor asks to see: Four quarters of internal scan reports covering all in-scope system components; Rescan reports showing high-risk and critical findings closed; Scan tool plugin or signature update logs; Vulnerability risk ranking criteria from Requirement 6.3.1. Where it usually falls short: A quarter missed or the scan scope omitted some CDE segments
External vulnerability scans must meet these conditions: they run at least every three months; an Approved Scanning Vendor (ASV) listed by the PCI SSC performs them; with vulnerabilities resolved and the ASV Program Guide conditions for a passing scan met; and with rescans run as needed to confirm resolution under those passing-scan conditions. Applicability: for the first PCI DSS assessment against this requirement, four passing scans within 12 months are not required if the assessor confirms (1) the latest scan passed, (2) documented policies and procedures mandate quarterly scanning, meaning at least every three months, plus (3) rescans show the reported vulnerabilities were fixed. From the second year onward, a passing scan is needed for every three-month period. Details of the target environment (load balancers, third parties, ISPs, configurations, protocols, scan interference) are for the ASV and the scan customer to settle between them, with the ASV Program Guide describing scan customer responsibilities. Customized approach objective: not eligible for the customized approach.
What an assessor asks to see: Four quarterly passing ASV scan reports with attestation of scan compliance; Rescan reports demonstrating failed items were fixed; Evidence the ASV is on the PCI SSC approved list; External IP and domain scope list agreed with the ASV. Where it usually falls short: A quarter with only a failing scan and no passing rescan
Requires vulnerability monitoring and scanning of the system and hosted applications at a defined frequency or randomly by a defined process and when new relevant vulnerabilities are reported, using tools and techniques that support standardised enumeration, checklists and impact measurement, with results analysed, remediation within defined response times by risk, results shared with defined personnel, and privileged scanning access where required.
What an assessor asks to see: Scan schedule and coverage evidence across the system and hosted applications; Scan reports with findings ranked by severity; Defined remediation timeframes by risk level and evidence they are met; Records of scan result distribution to the defined personnel. Where it usually falls short: Unauthenticated scanning only, which understates the real vulnerability position
Obtain vulnerability information, evaluate exposure, and take appropriate remediation.
Guidance beside it, ISO 27002 8.8: Requires information about technical vulnerabilities in the information systems in use to be obtained, the organisation's exposure to them to be evaluated, and appropriate measures to be taken. Older source material sets out the surrounding process: named roles and responsibilities, identified information sources, a defined reaction timeline, assessment of the risk posed by the vulnerability against the risk of applying the patch, testing before deployment, alternative measures where no patch exists, an audit log of actions taken, and highest risk systems addressed first.
What an assessor asks to see: vulnerability_feed_logs; risk_assessment_reports; remediation_ticket_records; patch_deployment_evidence. Where it usually falls short: Relying on ad-hoc scans only
Two duties travel together in this point. The first is that security is built into how systems are acquired, developed and maintained: security requirements set before purchase or build, secure development practice, change control, and maintenance that does not quietly reintroduce weakness. The second is vulnerability handling and disclosure, meaning the entity can receive a vulnerability report about its own products or systems, triage it, fix it on a timescale that reflects severity, and handle disclosure. A published route for a finder to reach the entity is the part most often missing, and its absence is visible from outside. Note that the coordinator role and the European vulnerability database in Article 12 belong to the CSIRTs and ENISA; what binds the entity is its own handling and disclosure capability.
What an assessor asks to see: Security requirements applied in procurement and in the development lifecycle, with gate evidence; Secure development practices in use, such as design review, code analysis and dependency scanning, with output; Change and maintenance control records for in-scope systems; A published contact route for vulnerability reports, and the triage procedure behind it. Where it usually falls short: Security requirements defined for new build only, leaving acquired and inherited systems untouched
Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register