SOC 2 Application Pentest
A penetration testfor your SOC 2 audit,at a fixed price.
Layer8 tests one web application and the first-party API of the same product for a fixed price and a fixed scope. The engagement runs by email, without kick-off or debrief calls. Testing combines the AI assessment platform Layer8 developed in-house with external AI services, and a security engineer reviews your scope before testing starts, the results as they come in, and every report before it is released.
- Price
- USD 2,500, one-time
- Standard turnaround
- First report five business days from the agreed start date
- Deliverables
- English reports, SOC 2 criteria mapping, attestation letter
- Retest
- One retest within 30 days of the report
This service does not guarantee SOC 2 compliance or acceptance by your auditor. It provides the technical testing and evidence that audits commonly ask for.
Scope
One product, one environment
The standard scope covers one web application and the first-party API of the same product. Testing is grey-box, using up to three test accounts so that authenticated features and access control are covered. We confirm your target fits this scope before you pay anything.
Included in the standard scope
- One web application and the first-party API of the same product
- Grey-box testing with up to three test accounts or roles
- One environment, up to 100 endpoints
- Login via ID and password, email verification, TOTP or common SSO
- Access control, authentication, input handling and business logic
Not included in the standard scope
- Mobile applications, internal networks and physical devices
- Several independent products, or several environments at once
- Third-party assets you are not authorised to test
- Environments that require VPN access and cannot allowlist a Layer8 fixed IP
- Load testing, denial of service and availability testing
Deliverables
Reports your auditor and your developers can both use
We report confirmed findings only. Speculative results that we could not validate are never shown to you. A Layer8 engineer approves each document before it is released, and we reissue the reports after the retest.
- Executive report
- Scope, testing window, method, and the number and severity of findings, written for auditors and management.
- Technical report
- Reproduction steps, captured traffic, expected impact and remediation guidance for every finding, at the level of detail an engineer needs to start fixing.
- Reference mapping to SOC 2 Trust Services Criteria
- Each finding is mapped to the criteria it relates to, as reference information. The mapping does not replace your auditor's judgement.
- Attestation letter
- An English letter issued by Layer8 Co., Ltd. stating the scope, the testing window and the method used.
From request to report
No calls, and no testing before a person approves it
The engagement runs asynchronously by email. Starting the test, confirming critical and high findings and releasing the reports are all done by a Layer8 engineer. The turnaround runs from the start date we agree with you, not from the date you approve the order.
- You
Send the target details
Email us the target URL, the environment, whether the API is in scope and how many test accounts you can provide. No call is required at any point.
- Layer8
Confirm scope and terms
Within one business day we confirm the target fits the standard scope, then send the terms and the payment details. If it does not fit, we tell you before you pay.
- You
Authorise the test
Accept the Authorization to Test and the Rules of Engagement, and hand over the test accounts through an encrypted channel. Credentials are never collected over email. Once the conditions below are in place, we agree a start date with you.
- Layer8
Run the assessment
An engineer who reviewed the scope starts the test. Traffic and actions are logged throughout. If Layer8 becomes aware of a serious effect on the target, we interrupt the assessment ourselves and contact you.
- Layer8
Confirm findings and report
Critical and high findings are reviewed against their evidence and re-confirmed where it is safe to do so. Critical findings are sent to you as soon as they are confirmed, without waiting for the final report.
- You
Fix and retest
Within 30 days of the report you can request one retest of the findings we originally reported.
What has to be in place before the start date is fixed
- Scope, authorisation to test and the testing conditions are agreed
- Payment is confirmed
- The test accounts and documents we need have been received
- We have confirmed that the target is reachable and the test accounts can log in
- Scope review
- Within one business day
- Standard turnaround
- First report five business days from the agreed start date
- Retest turnaround
- Three business days after the request is confirmed
- Communication
- Email only, fully asynchronous
Controls
Prohibited actions are fixed before testing starts
Production targets are accepted conditionally, after we review the possible impact. Prohibited actions, rate limits, testing windows and emergency contacts are agreed in advance and enforced during the test.
- Prohibited actions
- No denial of service, load testing or high-volume traffic. No data deletion, no notifications or email to real customers, and no real payments, transfers or contracts.
- Data we use
- Only the test accounts and test data you provide. Write operations are limited to the features you explicitly allow.
- Rate and timing
- The rate limits, testing windows and prohibited features you specify are applied to the test configuration and enforced while it runs.
- If testing affects your system
- If Layer8 becomes aware of a serious effect on the target, we interrupt the assessment ourselves and contact you. Backups, recovery options and emergency contacts are confirmed before testing begins.
- Stop requests from you
- The contact point for a stop request, the hours it is reachable and the procedure that follows are agreed in the Rules of Engagement before testing starts.
- AI and external services
- The AI assessment platform Layer8 developed in-house is combined with external AI services, and a security engineer reviews the results. Data sent to those services is processed with training and retention turned off.
- What cannot be tested safely
- Anything that cannot be validated safely is recorded in the report as Not Tested or Staging Only.
Pricing
USD 2,500, one-time
There is one price. No subscription, no per-account fees, and no separate charge for the retest. Pricing and invoicing are in USD. If you need another currency or a larger scope, contact us about a standard penetration testing engagement.
USD 2,500 One-time, excluding tax
Included in the price
- Scope review and authorisation checks
- Testing of the web application and its first-party API
- Engineer review of critical and high findings, with critical findings notified early
- Executive report and technical report, both in English
- Reference mapping to SOC 2 Trust Services Criteria
- Attestation letter issued by Layer8 Co., Ltd.
- One retest within 30 days of the report, plus report v2
What this price assumes
- Reachability
- The target is reachable from the internet, or can allowlist a Layer8 fixed IP. Environments that require VPN access are out of scope.
- Authentication
- ID and password, email verification, TOTP and common SSO are supported. CAPTCHA is disabled for the test accounts.
- Test accounts
- You provide up to three accounts with different roles, along with test data we are allowed to modify.
- Environment
- Staging is recommended. Production is accepted conditionally, once prohibited actions, rate limits, testing windows and emergency contacts are confirmed.
Refunds
If we cannot test it, you get your money back
Payment places the order; it does not commit us to testing a target we cannot test safely or lawfully. When our review says we cannot proceed, we refund in full.
- Full refund
- The target does not fit the standard scope, authorisation cannot be confirmed, testing cannot be carried out safely, or you cancel before testing starts.
- No refund
- Once testing has started we do not refund. Testing starts when Layer8 has approved the scope and an engineer has begun the assessment.
- Retest boundary
- A retest covers only the findings we originally reported. New exploration or additional scope is a separate engagement.
FAQ
Questions to settle before you start
What the service covers, how it relates to SOC 2, and how your data is handled.
Does this make us SOC 2 compliant?
No. We do not guarantee compliance or acceptance by your auditor. We provide the testing record, the reports and an attestation letter that audits commonly ask for. Which evidence your auditor accepts is their decision.
Can you test production?
We recommend staging. Production is accepted conditionally, once prohibited actions, rate limits, testing windows and emergency contacts are confirmed.
What if our scope is larger than the standard service?
We tell you before you pay. If it only becomes clear after payment, we refund in full. For larger applications we can quote a separate engagement.
How do we hand over test account credentials?
Never by email. You submit them through an encrypted channel we send you. They are accessible only to the engineers who need them, and they are deleted within 30 days of the first report being issued.
What happens to our data after the assessment?
Credentials, raw traffic logs and temporary files held by Layer8 are deleted within 30 days of the first report being issued; anything collected during a retest is deleted within 30 days of the retest report. Those files are kept in storage we do not back up, so deleting them leaves no copy behind. Reports and the evidence needed to support them are retained for one year from issue, with credentials excluded and identifying details masked; we do not undertake to delete backup copies of those immediately, and they expire with that retention period. Data sent to external AI services is processed with training and retention turned off.
Can you delete it earlier than that if we ask?
We confirm that the request comes from someone authorised to make it, then tell you what can be deleted and when. A report deleted early is excluded from any later reissue.
Could testing affect our service?
Given the nature of penetration testing we cannot rule out any impact. That is why rate limits, concurrency, testing windows and prohibited actions are fixed in advance, and why the stop procedure, the contact point for it and the hours that contact is reachable are agreed before testing starts. If Layer8 becomes aware of a serious effect on the target, we interrupt the assessment ourselves and contact you.
How long do we keep access to the reports?
We keep the reports available for one year from issue and reissue them on request, with credentials excluded and identifying details masked.
Do you use AI to run the assessment?
Yes. Layer8 combines the AI assessment platform it developed in-house with external AI services, and a security engineer reviews the results before anything is reported. Requests, responses and code fragments from the target may be processed by those external services for analysis, with training and retention turned off.
Do you hold kick-off or debrief calls?
Not for this service. It runs asynchronously by email. If you need calls or a results walkthrough, contact us about a standard penetration testing engagement instead.
Get started
Send us the target, and we confirm the scope in one business day
Tell us the target URL, the environment and whether the first-party API is in scope. We confirm whether it fits the standard service, then send the terms and payment details. No call is required.
Self-serve checkout is in preparation. Until it is available, orders are handled by email.