External compliance assessment
Know where you stand before an auditor or a customer asks.
It starts from each control in your framework and works backwards to what can be verified from the internet. It covers the assets on your boundary, like mail, web, APIs, remote access, and DNS, and determines the software versions, encryption levels, and configurations that map to the framework.
Who does the work
John has been on both sides of the assessment.
On one side, he ran third-party risk assessments of 171 companies at a Fortune 200 global bank. On the other:
Mergers and Acquisition
Acquired by a customer
John led the company's HITRUST r2 assessment from the inside: the gap assessment, remediating the controls that had to pass in each domain, and assembling the evidence for the assessors. That certification won customer trust and gave Optum, already a customer, the confidence in the company's systems to acquire it.
He has also been through a HIPAA assessment that ended with a CPA firm's certificate.
How they build on each other
Each step can lead to the next.
01
A finding
Something we observed from the outside and emailed you about.
The whole outside view, mapped to your framework.
The inside view: your policies, controls, and the evidence behind them.
Scoped from what the assessments found.
The business case
Enterprise security reviewers and cyber insurers often check what you expose to the internet before they ask you anything. Seeing it first means you fix it before it comes up in a deal or a renewal.
The compliance case
Supporting evidence for:
- SOC 2 CC3.2, CC4.1
- HIPAA §164.308(a)(1)(ii)(A), §164.308(a)(8)
- ISO 27001 A.5.35
- NIST CSF ID.IM-01
- NIST 800-53 CA-2
References are to the 2017 Trust Services Criteria for SOC 2, the HIPAA Security Rule at 45 CFR Part 164, ISO/IEC 27001:2022 Annex A, NIST CSF 2.0, and NIST SP 800-53 Rev. 5.
Pricing
A fixed fee, quoted after a 30-minute scoping call.
What moves the price:
- The framework
- Company size, and how many systems, cloud accounts, or domains are in scope