A penetration test looks for exploitable weaknesses in software, APIs, and attack paths. A cryptographic review evaluates whether the underlying authentication or encryption mechanisms can be weakened by subtle implementation or library issues. A SOC 2 Type II audit examines whether controls are appropriately designed and operating effectively over time.
How each assessment type is meant to answer a different question
A penetration test asks where an attacker can actually get in and what they can do after entry. A cryptographic review asks whether the trust built into authentication, signatures, key handling, or encryption can be undermined by implementation choices rather than by obvious configuration errors. A SOC 2 Type II audit asks whether the control environment is designed well and then operated consistently across the audit period.
That means the three activities can overlap in scope, but they are not substitutes. One is adversarial and technical, one is control- and implementation-focused, and one is assurance-oriented. The same system can pass one and still fail another, depending on whether the issue is exploitability, cryptographic soundness, or evidence of operating effectiveness.
What a penetration test is trying to prove
A penetration test is evidence-driven attack simulation. It is used to validate whether weaknesses in applications, APIs, infrastructure, or access paths can be chained into real compromise, and whether compensating controls actually slow or stop exploitation. For a scoped engagement, the goal is not broad assurance but a credible demonstration of exploitability under defined rules of engagement, which is why clear authorisation and scope are part of the work itself. See the Penetration Testing Guide for the practical distinctions between test types and reporting expectations.
A good pentest focuses on attack paths, privilege gain, lateral movement, exposed services, and the quality of detection or response along the route. It is especially useful when you need to know whether a specific weakness can be weaponised, not just whether a control exists on paper. The same reason to scope carefully also applies to Penetration Test Scoping Checklist, because poor scoping can make a test look successful while missing the exposures that matter most.
What a cryptographic review is actually checking
A cryptographic review is narrower and more specialised than a general security test. It examines whether the system’s cryptographic design and implementation preserve the security properties they are supposed to provide, such as confidentiality, integrity, authentication, and resistance to tampering. The concern is often not “is encryption present?” but “is it used correctly, with safe parameters, safe libraries, safe key handling, and no subtle implementation flaw that collapses the protection?”
This is why cryptographic review can surface issues a pentest might not. A system may be hard to exploit conventionally yet still rely on weak algorithm choices, insecure nonce handling, flawed certificate validation, or poor token/signature verification. It is a technical assurance activity around trust primitives, so the practitioner question is usually whether the cryptographic design actually supports the security claim the product is making. For broader key lifecycle context, the SOC 2 Trust Services Criteria (AICPA) page helps show where confidentiality and security expectations sit in an assurance model, even though the cryptographic review itself is more implementation-oriented.
What a SOC 2 Type II audit is proving over time
An SOC 2 Type II audit does not try to break the system. It assesses whether a service organisation’s controls are suitably designed and then operating effectively throughout a defined period. That shifts the emphasis from a point-in-time snapshot to repeatable control execution, evidence quality, exceptions, remediation, and consistency of operation. The subject is control assurance, not exploit discovery.
In practice, a Type II audit asks whether the organisation can show that access, change management, logging, monitoring, incident handling, and related controls were not just documented but actually performed as intended. The SOC 2 Guide is the most direct internal resource for understanding Type 1 versus Type 2, scoping, carve-outs, CUECs, and evidence expectations, while SOC 2 Readiness Checklist is useful when you need to translate the report requirement into operational preparation.
Risk and Threat Considerations
The practical risk is confusing these activities and drawing the wrong conclusion from the wrong test. A strong pentest does not prove a control environment is operating effectively over time, and a clean audit does not prove that a targeted exploit path does not exist. Cryptographic weaknesses can also remain hidden if the review is too shallow or if the issue is in a rarely exercised code path.
Failure mechanism: Organisations often treat one assurance activity as coverage for the others, so real exploitability, cryptographic failure, or control drift can remain undiscovered until an incident, assessment, or customer review exposes it.
Impact: The result can be a false sense of security, delayed remediation, audit exceptions, or a control story that does not match the real technical risk profile of the system.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP ASVS and NIST SP 800-53 Rev 5 set the technical controls, while SOC 2 (AICPA) defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V11 — Cryptography | Cryptographic review focuses on implementation soundness of encryption and trust primitives. |
| Recommendation — Review cryptographic design and implementation for safe algorithms, parameters, and verification logic. | ||
| NIST SP 800-53 Rev 5 | CA-8 — Penetration Testing | Penetration testing is the direct control activity for validating exploitability. |
| Recommendation — Plan and execute penetration tests against in-scope systems to validate exploitable paths and weaknesses. | ||
| SOC 2 (AICPA) | CC6.1 — Logical Access Security Software and Infrastructure | SOC 2 Type II evidence depends on controls operating effectively over the audit period. |
| Recommendation — Collect evidence that logical access controls operated consistently throughout the reporting period. | ||
Practitioner Guidance
What to verify: If you need real assurance, verify that the engagement objective matches the question being asked. Use a pentest when you need exploit paths, a cryptographic review when you need trust primitive assurance, and a Type II audit when you need evidence of control operation over time.
Decision rule: If the main concern is “can this be broken?”, prioritise penetration testing. If the main concern is “is the cryptography sound and correctly implemented?”, prioritise cryptographic review. If the main concern is “can we demonstrate ongoing control operation to an external assessor?”, prioritise the SOC 2 Type II audit evidence set.
Practitioner takeaway: The fastest way to misread assurance is to assume all three outputs answer the same question, because each one measures a different failure mode and each one can be true while the others are not.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org