Preparing for an ISO 27001 audit requires more than exporting the latest vulnerability report. Auditors typically need to understand what was scanned, why it was in scope, how findings were assessed, what remediation occurred, and whether the results were independently verified. This guide provides a practical evidence model for vulnerability scanning, including a control-to-record mapping, recurring checkpoints, an inventory register, remediation verification fields, and a method for documenting risk-based exceptions without suggesting that scanning alone proves certification.
Overview
ISO 27001 certification evaluates an organization’s information security management system (ISMS), not one security product or one point-in-time scan. Vulnerability scanning can support the ISMS by demonstrating that the organization identifies technical weaknesses, evaluates risk, assigns treatment, and checks whether agreed actions were completed.
The exact evidence expected depends on the organization’s scope, risk assessment, Statement of Applicability, policies, procedures, technology environment, and auditor. Treat this article as an evidence-planning framework rather than a list of universally mandatory documents. Confirm the applicable requirements and audit expectations with the person responsible for your ISMS.
A useful evidence package should answer five questions:
- Coverage: Which applications, APIs, servers, cloud resources, containers, repositories, and environments were included?
- Cadence: How often are scans performed, and what events trigger an additional scan?
- Risk: How are findings evaluated in the context of business impact, exposure, exploitability, and compensating controls?
- Action: Who owns each finding, what deadline applies, and what treatment decision was made?
- Verification: How does the organization confirm that remediation worked or that an approved exception remains justified?
Keep evidence traceable. A scan result should connect to an asset record, a finding or ticket, a risk decision, and a closure or exception record. If those links exist only in a person’s memory or across disconnected spreadsheets, audit preparation becomes slower and less reliable.
What to track
Control-to-record mapping
Map scanning activities to the ISMS processes and applicable control objectives that they support. Avoid claiming that a single scan “satisfies” an ISO requirement. Instead, describe the activity, its purpose, and the records it produces.
| Activity or evidence area | Records to retain | What the records should demonstrate |
|---|---|---|
| Asset and service inventory | Inventory export, ownership record, scope notes, environment classification | The organization knows which assets require assessment and who is accountable for them. |
| Scanning procedure | Approved procedure, schedule, scan configuration, exclusions, authentication method | Scanning is planned, repeatable, and appropriate to the environment. |
| Automated security scanning | SAST, SCA, DAST, API, container, cloud, or infrastructure scan results | Relevant technical checks are performed against defined targets. |
| Risk assessment and prioritization | Severity model, business-context notes, risk acceptance criteria, triage history | Findings are assessed using a consistent and explainable method. |
| Remediation management | Tickets, assigned owners, target dates, linked code or change records, status history | Findings are converted into accountable treatment actions. |
| Remediation verification | Rescan result, test output, reviewer approval, deployment reference | Closure is based on evidence rather than an unverified status change. |
| Exceptions and residual risk | Exception request, rationale, risk owner, expiry date, compensating controls, review record | Unresolved risk is visible, authorized, time-bound, and monitored. |
Sample scan-inventory register
Maintain a register that shows how each important asset or delivery surface is covered. The register can live in a governance platform, ticketing system, spreadsheet, or security scanner, provided changes are controlled and records can be retrieved.
| Field | Example entry |
|---|---|
| Asset or service | Customer portal API |
| Owner | Platform engineering |
| Environment | Production and pre-production |
| Technology and scan type | REST API; authenticated DAST and dependency scanning |
| Last completed scan | Date, time zone, tool or pipeline run identifier |
| Expected cadence | Defined by the approved procedure and risk assessment |
| Coverage limitations | Excluded administrative endpoint; separate manual review recorded |
| Open high-risk findings | Count, ticket references, target dates, exception references where applicable |
| Evidence location | Controlled link to report, ticket, and verification record |
Include the scan configuration, not only the headline result. A report without target scope, authentication status, timestamp, version, or exclusions may be difficult to interpret later.
Remediation verification template
For each closed finding, retain a compact verification record containing:
- Finding identifier, affected asset, and original discovery date.
- Original evidence, severity, business impact, and assigned risk rating.
- Remediation action, responsible owner, completion date, and related change or pull request.
- Verification method, such as a targeted rescan, full scan, test case, configuration check, or code review.
- Verification result, evidence location, reviewer, and review date.
- Any residual risk, accepted limitation, or follow-up action.
For false positives, preserve the analyst’s reasoning and supporting evidence. “Not exploitable” is more useful when accompanied by the affected code path, environmental condition, compensating control, or test result that supports the conclusion.
Cadence and checkpoints
Use a recurring review cycle so evidence is assembled during normal operations rather than recreated immediately before an audit. A practical schedule can include the following checkpoints:
- Per release or deployment: Review relevant CI/CD security scanning results, new dependencies, exposed endpoints, infrastructure changes, and security gate exceptions.
- Monthly: Reconcile the asset inventory with scan coverage, review overdue remediation, inspect repeated findings, and confirm that critical evidence links still work.
- Quarterly: Review scan coverage against the ISMS scope, validate owners and risk ratings, examine exception expiry dates, and sample closed findings for verification quality.
- Before an internal review: Select representative evidence from different asset types and environments. Check whether an unfamiliar reviewer could follow each finding from discovery to treatment.
- Before an external audit or surveillance review: Freeze a clearly labeled evidence set, document any open actions, and prepare a short explanation for scope changes, missed scans, tooling migrations, and approved exceptions.
Retention should follow the organization’s documented information-control policy and any applicable contractual or legal requirements. Do not create a special retention period solely for an audit unless it has been approved and consistently applied.
How to interpret changes
Changes in scan results do not automatically indicate that security has improved or deteriorated. A higher finding count may reflect newly added assets, a scanner update, broader authentication coverage, a new vulnerability disclosure, or reduced false-positive suppression. A lower count may result from risk acceptance, asset removal, deduplication, or a change in scan scope.
When a recurring metric changes, record the reason alongside the number. Useful measures include scanned assets versus in-scope assets, scan completion rate, new findings by risk tier, overdue findings, median age of open findings, verified closure rate, reopened findings, and exceptions approaching expiry. Interpret these measures with operational context rather than using one metric as a certification score.
Baseline changes carefully. If a team introduces a new API security scanner, container security scanning workflow, or software composition analysis tool, label the transition period. Compare like with like where possible, and preserve the old report or configuration so an auditor can understand why the numbers changed.
Risk-based vulnerability management is especially important when remediation cannot happen immediately. Document why the finding matters, what makes the exposure acceptable for the stated period, which controls reduce the risk, who approved the decision, and when it must be reviewed. An exception should expire or be renewed deliberately; it should not remain open because a ticket was never revisited.
When to revisit
Revisit this evidence model at least annually and whenever the ISMS scope, risk assessment, technology stack, audit program, or scanning process changes. A review is also appropriate after a major incident, migration to a new application security scanner, significant cloud or container adoption, acquisition of a new business system, or a change in development and deployment practices.
Use this practical end-of-cycle checklist:
- Confirm that the asset and service inventory matches the current ISMS scope.
- List every scanning method used and identify its covered and uncovered surfaces.
- Sample recent reports for timestamps, target scope, configuration, authentication status, and exclusions.
- Trace a selection of findings from discovery through triage, remediation, and verification.
- Review overdue findings and exceptions for owners, rationale, compensating controls, and expiry dates.
- Check that closed findings have verification evidence rather than status changes alone.
- Record tooling, scope, cadence, or process changes so future reviewers can interpret trend data.
- Confirm that evidence access and retention follow approved organizational policy.
Keep the final package understandable to someone who did not perform the scans. Clear ownership, consistent identifiers, explicit limitations, and linked remediation evidence make vulnerability scanning records more useful for both daily security operations and ISO 27001 audit preparation. Scanning supports an ISMS; it does not, by itself, establish certification or replace the organization’s broader risk-management and governance evidence.