Vulnerabilities, scans and penetration tests

A vulnerability is a weakness attackers can use. Scans find them automatically; penetration testers find them by trying to break in.

// TECH FOR GRC

The words

  • Vulnerability: a weakness, such as outdated software with a known flaw, or a bad setting.
  • CVE: the public ID given to a known vulnerability.
  • CVSS: a severity score from 0 to 10. Policies set fix deadlines by severity, for example critical in 7 days and high in 30.
  • Misconfiguration: a setting left unsafe, such as a public storage bucket. Cloud tools such as AWS Security Hub and Defender for Cloud flag these.

Scan vs penetration test

  • A scan is automated, frequent and broad. It finds known problems.
  • A penetration test is people trying to break in, usually yearly or before a major release. It finds what scanners miss, such as flaws in how an application works.

Companies need both, and auditors ask for both.

What this means for evidence

  • Scan results for the period, with severity and dates.
  • A ticket for each serious finding, with an owner.
  • Fix dates compared with the policy's deadlines. Late criticals are exceptions.
  • The penetration test report, plus proof the findings were fixed.

A dashboard showing a score is not enough. Auditors need the findings and what happened to each one.

// WHAT IT LOOKS LIKE AS EVIDENCE
Security Hub findings tracked to a ticketAWS Security Hub · proves CC7.1, A.8.8, A.8.9
AWS Security HubSAMPLE
Security Hub › Findings

Findings: severity Critical and High

complyoo-prod (4821 0093 1176)Exported 2026-10-01 10:02 UTC1
SeverityTitleResourceCreatedWorkflow2Ticket3
CRITICALSecurity group allows 0.0.0.0/0 on port 5432sg-0a91 (db-prod)2026-09-12RESOLVEDSEC-412
HIGHEC2 instance has a CVE score 8.8 packagei-07f2 (api-3)2026-09-20RESOLVEDSEC-418
HIGHIAM access key older than 90 daysdeploy-bot2026-09-25NOTIFIEDSEC-4214
  1. 1Export date. Findings change daily, so the date matters.
  2. 2Workflow status shows each finding was handled, not just detected.
  3. 3A ticket for every finding links detection to remediation.
  4. 4Open finding still inside the policy's fix window. The auditor will check the deadline.

Weak version: A dashboard score with no findings listed. A score shows nothing was fixed; the auditor needs the findings and their tickets.

// FROM A REAL ACCOUNTAWS console, AWS Config · identifiers blurred
Four AWS Config rules checking this account continuously: two pass, two fail. Security Hub runs most of its checks on this same engine, so this is the layer underneath its findings.
StrongFour AWS Config rules checking this account continuously: two pass, two fail. Security Hub runs most of its checks on this same engine, so this is the layer underneath its findings.
Open one failing rule and it names the resource: a security group with SSH open to the internet. That ID is what goes in the ticket, and the ticket is what the auditor follows.
WeakOpen one failing rule and it names the resource: a security group with SSH open to the internet. That ID is what goes in the ticket, and the ticket is what the auditor follows.
Defender for Cloud recommendations with ownersMicrosoft Defender for Cloud · proves CC7.1, A.8.8, A.8.9
Microsoft Defender for CloudSAMPLE
Defender for Cloud › Recommendations

Recommendations: High severity

Subscription: complyoo-prodExported 2026-10-02 09:05 IST1
RecommendationSeverityResourcesStatus2OwnerDue date3
Storage accounts should restrict network accessHigh1 of 6Completedmaria.s2026-09-15
Machines should have vulnerability findings resolvedHigh2 of 14In progressdavid.e2026-10-10
  1. 1Export date and subscription.
  2. 2Status shows progress, not just detection.
  3. 3Owner and due date make it a managed control.

Weak version: No owners or dates. Findings with no one responsible are just a list.

// REMEMBER THIS

Found, rated, owned, fixed on time. That is vulnerability management.

// CHECK YOURSELF

1. What does CVSS measure?

2. Which finds flaws in how an application's logic works?

3. The policy says critical fixes in 7 days. One took 19. That is...