Service · Compliance and regulatory reports
Security reports your auditor and regulator can work with
We deliver readiness assessments, penetration test reports and evidence packs that support audit, certification and licensing requirements, in English or Spanish, signed by our security director. They support the evidence for your audit; they are not a certification, an attestation or a regulatory approval.
Three deliverables, one standard of evidence
-
Readiness assessments
Where you stand against the testing requirements of a framework or regulation, and what to fix first.
-
Penetration test reports
External and internal tests with scope, methodology, findings with evidence and retest status, signed by our security director.
-
Evidence packs
Findings, retests and remediation history, organized for your auditor, your internal audit team or your regulator.
What we support, and what we do not do
| Framework or regulator | What we support | What we do not do |
|---|---|---|
| SOC 2 | Readiness, penetration testing and evidence for the Trust Services Criteria your auditor maps testing to, such as CC4.1 and CC7.1 | Issue the SOC 2 report: only a licensed CPA firm can |
| ISO/IEC 27001:2022 | Evidence for Annex A 8.8, management of technical vulnerabilities | Certify you: that is your certification body’s role |
| PCI DSS 4.0 | Internal and external penetration testing for requirement 11.4 | Quarterly external scans for 11.3: we are not an Approved Scanning Vendor |
| NRP-23, El Salvador | Vulnerability and intrusion testing under Art. 20 lit. i), with a signed report in Spanish | Accept or approve the report: that is the regulator’s decision |
| CNBV ITF, Mexico | Independent penetration testing and reports for Article 64 | Take over your reporting obligations to the CNBV |
| NIS2 and DORA | Testing evidence for NIS2 Art. 21(2)(f) and DORA Art. 24–25 | Threat-led penetration testing (TLPT) under DORA Art. 26 |
Signed by our security director
Every report is signed by our security director, who holds a postgraduate degree in information security and cryptography, a master’s degree in cyber defense and more than 20 years of experience.
Each report names its scope, methodology, testing modes and proof levels, so a reviewer can see exactly what was tested, how, and what the evidence shows. Signals that were not proven are labelled as such; they are never presented as findings.
From requirement to signed report
-
Map the requirement
Which norm applies, which systems are in scope and which deadlines you face.
-
Test
Continuous external testing, plus internal testing by our in-house team where the requirement calls for it.
-
Evidence and triage
Findings Validated with evidence; Signals reviewed by the team and labelled for what they are.
-
Signed report
In the language you need, structured around the requirement you need to support.
-
Remediation and retest
Help with your remediation plan and retests that show what was fixed, within your deadlines.
In the language your regulator or auditor reads
Latin American regulators expect reports in Spanish; international auditors and customers often expect English, and other markets have their own requirements. We deliver the language you need, or several, from the same evidence.
Questions about compliance reports
Can you issue our SOC 2 report?
No. Only a licensed CPA firm can issue a SOC 2 report. We help you arrive at that audit with testing and evidence in order.
Will the regulator accept your report?
Acceptance is the regulator’s decision. We structure each report around the requirement it supports, and we tell you what it covers before you engage us.
Do you perform the internal part of the testing?
Yes. Internal tests are always performed in-house by the NorthBound team.
Can you meet our deadline?
Tell us the date when you request access, and we will confirm what is feasible during scoping.
Find it before an attacker does.
Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.
Facts on this page verified 11 November 2026.