💳PCI DSS 6.2Rule: PCI-6-2critical

Security Patching

Description

Critical security patches must be installed within one month of release; other applicable security patches within 3 months.

⚠️ Risk Impact

Unpatched known vulnerabilities are weaponized within days of disclosure. CDE systems must be patched faster than general enterprise systems due to the high-value target nature.

🔍 How EchelonGraph Detects This

PCI-6-2Automated scanner rule

EchelonGraph's Tier 1 Cloud Scanner automatically checks for this condition across all connected cloud accounts. Violations are flagged as critical-severity findings with remediation guidance.

🔧 Remediation

Automated patching where possible. SLA tracking. Document exceptions. Continuous CVE scanning across CDE workloads, containers, and dependencies.

💀 Real-World Attack Scenario

Equifax 2017: Apache Struts CVE-2017-5638 disclosed March, exploited starting May. Equifax took 60+ days to patch the affected app. 147M records exfiltrated. PCI 6.2 violation (along with multiple others). Total cost: $1.4B+.

💰 Cost of Non-Compliance

Equifax: $1.4B+. Avg unpatched-vuln CDE breach: $4.45M.

📋 Audit Questions

  • 1.Patch SLA tracking?
  • 2.Current MTTR by severity?
  • 3.Walk through a Critical CVE — detection-to-remediation timeline?
  • 4.Exception list current?

🎯 MITRE ATT&CK Mapping

T1190 — Exploit Public-Facing Application

⚡ Common Pitfalls

  • SLAs documented but MTTR unmeasured
  • Exception list accumulates without renewal
  • Patching infra but not application deps

📈 Business Value

Disciplined patching = highest-ROI security investment.

⏱️ Effort Estimate

Manual

Ongoing per-CVE remediation

With EchelonGraph

EchelonGraph correlates CVEs to live CDE workloads; tracks SLA

🔗 Cross-Framework References

SOC2-CC6.8NIST-SI-2

Automate PCI DSS 6.2 compliance

EchelonGraph continuously monitors this control across all your cloud accounts.

Start Free →