Skip to Content

SOC 2

What it is — SOC 2 (System and Organization Controls 2) is a framework developed by the American Institute of Certified Public Accountants (AICPA)  for managing customer data based on five trust services categories: Security, Availability, Processing Integrity, Confidentiality, and Privacy. SOC 2 Type II reports assess whether an organization’s controls operated effectively over a period of time.

Appsec relevance — Several Common Criteria (CC) within the Trust Services Criteria require vulnerability management, system monitoring, and risk assessment — areas where Detectify’s scanning and Surface Monitoring apply.

How Detectify Supports SOC 2

Trust Services CriterionWhat it requiresDetectify Capability
CC3.2The entity identifies risks to the achievement of its objectives across the entity and analyzes risks as a basis for determining how the risks should be managedCVSS-based vulnerability scoring, categorization by CWE and OWASP Top 10 (2013 and 2017), report history across scheduled scans. Covers web and API vulnerability risk; broader operational and business risks require additional assessment
CC7.1The entity uses detection and monitoring procedures to identify (1) configuration changes that introduce new vulnerabilities and (2) susceptibilities to newly discovered vulnerabilities24/7 Surface Monitoring with change detection, scheduled vulnerability scanning, integrations for alerting (Slack, PagerDuty, Jira, ServiceNow)
CC6.1The entity implements logical access security software, infrastructure, and architectures over protected information assetsDetects authentication bypass (CWE-287 , CWE-306 ) and runs product-specific access control and authorization checks (CWE-284 , CWE-285 , CWE-862 , CWE-863 )
CC6.6The entity implements logical access security measures to protect against threats from sources outside its system boundariesApplication Scanning and API Scanning detect exploitable vulnerabilities in internet-facing systems; Surface Monitoring identifies exposed services
CC7.2The entity monitors system components for anomalies that indicate malicious acts, natural disasters, or errorsSurface Monitoring detects changes in external attack surface (new domains, ports, technologies); not a full system monitoring solution
CC8.1The entity authorizes, designs, develops, configures, documents, tests, approves, and implements changesAPI-triggered scanning detects vulnerabilities introduced by changes; does not replace change management processes
CC6.3The entity authorizes, modifies, or removes access to data and technology based on rolesDoes not implement RBAC. Detectify itself provides multi-team RBAC for its own platform

What Detectify Covers

Detectify supports SOC 2 criteria on risk identification (CC3.2), detection of new vulnerabilities (CC7.1), and protection against threats from outside the system boundaries (CC6.6). Scheduled scans with report history support ongoing risk assessment. Surface Monitoring’s continuous asset tracking supports system monitoring requirements (CC7.2).

Scheduled scanning, finding status, and report history record vulnerability management as an ongoing process rather than a point-in-time exercise.

The organizational controls (CC1.x, CC2.x, CC5.x) that cover the control environment, communication, and control activities are outside the scope of technical security testing tools.

Complementary Tools You May Need

  • GRC platform — For CC1.x governance and CC5.x control activities documentation
  • SIEM — For CC7.1–CC7.2 security event monitoring
  • IAM — For CC6.1 logical access implementation
  • Change management — For CC8.1 change control processes
  • Endpoint and network security — For CC6.6 protection beyond web applications
  • SAST — For code-level vulnerability analysis

References

Last updated on