Security Compliance Testing | SOC 2, ISO 27001, PCI DSS Skip to main content
QAonTOP
Contact Us

Security Compliance Testing Services

Prove the security controls your framework requires are in place and actually work, before your auditor or customer asks.

We test your access control, logging, encryption and configuration against SOC 2, ISO 27001, PCI DSS, HIPAA or GDPR, help your team close the gaps, and organise the results into evidence an auditor can follow. We don’t certify you; we make sure you’re ready for the people who do.

  • SOC 2, ISO 27001, PCI DSS, HIPAA, GDPR
  • Controls tested, not just documented
  • Evidence mapped control by control
  • Free retest after fixes

[ Why security compliance testing ]

A written policy isn’t proof. A tested control is.

Your access policy says leavers lose access the same day. Your encryption policy says every backup is encrypted. Auditors and enterprise customers increasingly want to see that this is true in practice, with dates, records and test results. Security compliance testing checks each control against the framework you answer to, finds where practice and policy don’t match, and gives you the evidence to show they now do.

Need privacy, consent, audit trail or system validation testing? See regulatory compliance testing, or all security testing services →

01

No surprises in the audit

Gaps found and fixed months ahead, not in the auditor’s first week.

02

Controls that really work

Tested in your live setup, not just described in a policy.

03

Evidence in one place

Results mapped to each control, ready for auditors and questionnaires.

04

Compliant all year

Key controls rechecked between audits, so they don’t drift.

[ Frameworks ]

The frameworks we test against

Each one asks for different evidence. We test the security controls it requires and map every result back to it.

SOC 2

Security, availability and confidentiality criteria, with evidence collected over the audit period for Type II.

ISO 27001

Information security controls from Annex A, and the evidence your certification auditor will ask to see.

PCI DSS

Security requirements for systems that store, process or transmit card data, including scans and penetration tests.

HIPAA

Technical safeguards in the Security Rule: access, audit controls, integrity and transmission security for health data.

GDPR

Security of processing for personal data: encryption, access, resilience and regular testing of your measures.

[ What we test ]

Eight checks between you and a clean audit

Start with a gap assessment, then test the controls that matter for your framework. Each card lists what we check, when you need it and the problem it prevents.

Security gap assessment

Where you stand

We compare your current security controls with the framework you need to meet and give you a clear list of what’s missing, what’s partial and what’s already in place.

What we check
  • Controls mapped to SOC 2, ISO 27001, PCI DSS, HIPAA or GDPR
  • Interviews with the people who own each control
  • Evidence you already have, and what’s missing
  • A gap list with an owner and plan for each gap
When you need it

At the start, ideally months before an audit or renewal.

The problem it preventsFinding gaps during the audit instead of before it

Access control & authentication testing

Who can do what

We test whether access really works the way your policy says: the right roles, multi-factor sign-in where required, and accounts removed when people leave.

What we check
  • Role-based access in your apps and admin tools
  • Multi-factor coverage and password rules
  • Session timeouts and sign-out
  • Joiner, mover and leaver processes
When you need it

Before every audit, and after changes to roles or sign-in.

The problem it preventsFormer staff or the wrong roles still able to reach sensitive data

Logging & monitoring checks

Can you prove it?

We check that security-relevant events are logged, protected from tampering, kept for as long as required and actually reviewed.

What we check
  • Sign-in, admin and data access events
  • Log integrity and protection from changes
  • Retention periods against your requirements
  • Alerting and review of important events
When you need it

When auditors ask how you’d know if something went wrong.

The problem it preventsNo record of who accessed what, when it matters most

Encryption & data protection testing

Data in transit and at rest

We verify that sensitive data is encrypted where your framework requires it, that keys are managed properly and that data is deleted when it should be.

What we check
  • TLS settings and certificate handling
  • Encryption of databases, storage and backups
  • Key management and access to keys
  • Data retention and secure deletion
When you need it

When you store card, health or personal data.

The problem it preventsSensitive data readable by anyone who reaches it

Configuration & hardening checks

Servers and cloud

Servers, databases and cloud accounts checked against your agreed hardening baseline, so default settings and drift don’t undo your controls.

What we check
  • Cloud account and network settings
  • Server, database and service configuration
  • Default accounts and unused services
  • Drift between environments over time
When you need it

Before audits and after infrastructure changes.

The problem it preventsOne misconfigured system failing an entire control

Most frameworks expect regular vulnerability scans and penetration tests, with proof that findings were fixed. We run them and keep the records auditors ask for.

What we check
  • Scheduled vulnerability scans in scope
  • Penetration testing where your framework requires it
  • Fix timelines by severity
  • Retest and closure records
When you need it

Quarterly, and before audits and renewals.

The problem it preventsScans that ran but no proof anything was fixed

Evidence packs & security questionnaires

Audit-ready

We organise test results, screenshots and records into an evidence pack mapped to each control, and help you answer customer security questionnaires from it.

What we check
  • Evidence mapped control by control
  • Test records with dates and owners
  • Reusable answers for customer questionnaires
  • A summary your auditor can follow
When you need it

Ahead of audits and large customer security reviews.

The problem it preventsWeeks lost chasing evidence and rewriting the same answers

Continuous compliance checks

Release by release

Key security controls retested on a schedule and after major releases, so you stay compliant all year, not just in audit season.

What we check
  • Control checks linked to your release cycle
  • Quarterly access and configuration reviews
  • Evidence collected as you go
  • Alerts when a control slips
When you need it

For SOC 2 Type II and other frameworks that look at a whole period.

The problem it preventsPassing in March and drifting out of compliance by June

Scans and pen tests in detail: vulnerability assessment and penetration testing →

[ Our role vs your auditor ]

We prepare you. Your auditor certifies you.

Being clear about roles avoids surprises. Here’s how security compliance testing fits with our regulatory compliance testing and with your audit.

AspectSecurity compliance testingRegulatory compliance testingExternal audit
FocusSecurity controls: access, logging, encryption, configurationLegal requirements: privacy, consent, audit trails, validationIndependent opinion on your controls
FrameworksSOC 2, ISO 27001, PCI DSS, HIPAA, GDPRGDPR, HIPAA, PCI DSS, 21 CFR Part 11 and moreThe one you’re being audited against
OutputTest results, gap list, evidence packRequirement-to-test traceability, evidenceReport or certificate
Who provides itQAonTOPQAonTOPAn accredited auditor or certification body

Want compliance as part of a wider, ongoing security plan? See cyber security testing →

[ How we work ]

Six steps from first gap list to audit-ready

Technical testing follows OWASP and NIST SP 800-115. Every result is dated, attributed and mapped to the control it proves.

  1. Step 1 of 6

    Agree framework and scope

    Which framework, which systems and which audit date. Scope and test windows are signed off before anything starts.

    You getSigned scope
  2. Step 2 of 6

    Gap assessment

    Controls mapped to the framework, owners interviewed and existing evidence reviewed.

    You getGap list with owners
  3. Step 3 of 6

    Test the controls

    Access, logging, encryption, configuration and vulnerability checks run against each requirement.

    You getTest results with CVSS ratings
  4. Step 4 of 6

    Close the gaps

    A remediation plan agreed with your team, with help while fixes are made.

    You getRemediation plan
  5. Step 5 of 6

    Retest and collect evidence

    Fixed gaps retested free of charge, with results added to the evidence pack.

    You getRetest reportEvidence pack
  6. Step 6 of 6

    Audit support

    Evidence handed over, questionnaire answers prepared and auditor questions answered.

    You getAudit-ready summary

NDA before access

We sign your NDA before we see any systems, records or evidence.

Honest about our role

We test and prepare; certification comes from your independent auditor.

Encrypted evidence

Reports and evidence are encrypted in transit and at rest, shared only with named people.

[ Deliverables ]

What you receive

Organised so your auditor can follow it and your engineers can act on it.

01

Gap assessment

What’s in place, partial or missing against your framework, with an owner for each gap.

02

Control test reports

Results for access, logging, encryption and configuration, with CVSS ratings where relevant.

03

Remediation plan

Fixes in priority order, timed against your audit date.

04

Evidence pack

Test records, screenshots and dates mapped control by control.

05

Questionnaire support

Reusable answers for customer security reviews, backed by real results.

06

Retest report

Proof that each fixed gap is closed, added to the evidence pack.

[ Tools ]

The tools behind our compliance testing

15 tools that produce clear evidence your auditor can follow, checked and explained by our testers.

Scanning & evidence

Known weaknesses found and documented.

04 TOOLS
  • NessusVulnerability scanning
  • OpenVASOpen-source scanning
  • AcunetixWeb vulnerability scanning
  • OWASP ZAPWeb app scanning

Cloud configuration

Settings checked against benchmark controls.

04 TOOLS
  • ProwlerAWS & Azure checks
  • ScoutSuiteMulti-cloud audit
  • KubescapeKubernetes security
  • TrivyContainer & IaC scanning

Code security

Secure development evidence.

04 TOOLS
  • SonarQubeStatic code analysis
  • CheckmarxEnterprise SAST
  • SemgrepCustom code rules
  • GitleaksSecrets in code

Tracking & evidence

Findings, fixes and proof in one place.

03 TOOLS
  • DefectDojoVulnerability management
  • JiraFindings & fixes
  • ConfluenceReports & docs

[ Case Studies ]

Security work we’ve delivered

Security testing was part of our QA work on these products, several in regulated sectors. Each links to the full write-up.

All case studies →

[ Ways to work ]

Six ways to get audit-ready

One-off audit preparation, checks all year round, or a security tester in your team.

Not sure which fits? Find your model in four questions, compare all six or estimate your cost.

[ FAQ ]

Security compliance testing questions, answered

{{ f.a }}

[ Contact us ]

Get ready for your next audit

✓ Free one-week POC✓ NDA before access✓ A QA lead replies the same day

[ Keep exploring ]

Related testing services

All services →