Resources
What each framework actually asks of security testing
Compliance is the reason most first penetration tests get bought, and the frameworks disagree about what they require. One names the test outright. Two never mention it. This page separates what each framework actually says from what assessors have come to expect, so you can scope the work to the evidence you genuinely need.
Five frameworks, honestly described
These are the frameworks we test and report against. Framework facts were verified against primary sources: the AICPA Trust Services Criteria, the PCI Security Standards Council’s penetration testing guidance, and the HIPAA Security Rule.
PCI DSS
Names the penetration test outright.Requirement 11.4 requires external and internal testing at least annually and after significant changes, on a documented, industry-accepted methodology. This is testing to a public specification.
- What assessors expect to see
- A scoped test of the cardholder data environment, segmentation validation, and evidence that findings were corrected. Your assessor also checks the methodology and the tester's independence.
SOC 2
Does not mandate a penetration test.The AICPA's Trust Services Criteria are control criteria your auditor evaluates your system against. How you demonstrate them is between you and your auditor. A recent, retest-verified pentest is simply the demonstration auditors accept most readily.
- What assessors expect to see
- Evidence that vulnerabilities are identified and addressed, operating across the review period for a Type 2 rather than existing on the day fieldwork starts.
HIPAA
Never says penetration test.The Security Rule is deliberately technology-neutral. It requires an accurate and thorough risk analysis and a periodic technical and nontechnical evaluation of safeguards. A pentest is how the technical half of that evaluation gets real evidence behind it.
- What assessors expect to see
- Assessment of the systems that carry protected health information, with remediation guidance an evaluator can follow.
ISO 27001
Expects risk-based controls that are tested and reviewed.We scope testing to the controls in your statement of applicability and report against them, so the assessment supports your certification body's review rather than duplicating it.
- What assessors expect to see
- Assessment reports mapped to the controls in scope, plus remediation and retest evidence across surveillance cycles.
GDPR
Expects appropriate technical measures for personal data.We produce security-testing evidence of the technical measures protecting personal data. We do not offer a legal opinion on your obligations, which sits with your counsel or data protection officer.
- What assessors expect to see
- Testing evidence covering the systems that process personal data, with findings and verified remediation.
Where we sit in your audit
We are an independent testing partner, never a certification body. We produce the evidence; the audit or certificate is issued by your assessor. On our own posture we are equally plain: we hold no organizational certification today and do not claim otherwise, and ISO 27001 certification for VirtuesTech is planned, stated July 2026. The trust page carries the full position, including what we do not have.
One engagement can feed several frameworks, because the artifact an assessor reads is largely the same: a scoped test, findings demonstrated with reproduction steps, and remediation verified on retest. That last part matters more than it sounds. A report that ends at reported leaves your assessor holding open risk, which is why retest is standard rather than an add-on.
Scoping the work to your deadline
If you know the framework and the date, the testing plan is worked backwards from both. The compliance and security audits service covers gap assessment and evidence preparation. To prepare for a scoping conversation, the scoping checklist lists what we will ask, and the report walkthrough shows what an assessor-ready deliverable contains, including a real finding reproduced in full.
Bring the audit date
Give us the framework and the deadline, and the testing plan gets worked backwards from both, with evidence formatted for your assessor to consume directly.