Skip to content
Trust and data

Your systems. Your rules.

We test only what you authorize, isolate every engagement inside single-tenant August Sandboxes, and never train AI models on your data.

AUGUST CYBER · WORKSPACE OPS
Verified ScopeDNS TXT + IP pinned 203.0.113.42:443
_august-verify.staging.meridian.io
Active Sandbox4 vCPU · netfilter LOCKED
sbx_41d9e02a
Session
00:41:07
3 reproduced · 2 retests verified

Any signed-in customer can read another customer's payout

CriticalBOLA · CWE-639GET /api/v1/payouts/:idReproduced 3 of 3
Reviewed · P. SharmaSenior Security Engineer
AActor Acustomer 1001Not the owner
01GET /api/v1/payouts/po_2002 HTTP/1.1
02Host: staging.meridian.io
03Authorization: Bearer eyJhbGciOi…c1001
04HTTP/1.1 200 OKExpected 403
05{
06 "id": "po_2002",
07 "owner": "cus_1002",
08 "amount": 1284000,
09 "iban": "GB29NWBK60161331926819",Leaked to A
10 "status": "paid"
11}
BActor Bcustomer 1002Owner
01GET /api/v1/payouts/po_2002 HTTP/1.1
02Host: staging.meridian.io
03Authorization: Bearer eyJhbGciOi…c1002
04HTTP/1.1 200 OKOwner baseline
05{
06 "id": "po_2002",
07 "owner": "cus_1002",
08 "amount": 1284000,
09 "iban": "GB29NWBK60161331926819",Owner data
10 "status": "paid"
11}
src/routes/payouts.ts:84db.payouts.findById(req.params.id)
No owner checkBodies match byte for byte · 148 B
Evidence ChainChain intact · 4 of 4 links
August Cyber / Trust

Before and during testing

  1. 01Zero active testing before a written Rules of Engagement is signed
  2. 02Test accounts you control, never real customers
  3. 03Dedicated egress allowlist IPs issued per engagement in the signed RoE
  4. 04Agreed time windows and immediate stop on request from either side
  5. 05No denial of service and no social engineering unless you sign for it
  6. 06Engineer-verified findings with a signed Letter of Attestation

Your data

  • Zero model training on your source code, traffic, prompts or findings
  • Zero data retention across CyberCART API prompts and completions
  • Scope-locked Linux VMs that reach only verified domains
  • We keep only the evidence required for your report and retest
  • 30-day artifact deletion on request, or earlier per your contract

Our promise ›

We behave like the attacker, never like a risk. You decide the scope. We prove what breaks, help you close it and leave nothing behind.

Architecture & Sandbox Isolation ›

Hard technical boundaries on every run.

Every assessment runs inside isolated single-tenant infrastructure enforced at the kernel, network and contract layers.

  1. 01Sandbox isolation

    Single-tenant August Sandboxes with kernel and DNS scope lock

    Every engagement runs inside its own single-tenant August Sandbox VM. Outbound networking is locked at the kernel firewall and DNS resolver strictly to domains you authorize, dropping all other egress by default.

  2. 02Egress allowlisting

    Dedicated egress allowlist IPs per engagement

    We do not share static public scanning pools across customers. Dedicated source egress IPs are provisioned per engagement and recorded in your signed Rules of Engagement before testing starts so your WAF and SOC can verify every request.

  3. 03AI data boundary

    Zero model training on client code or traffic

    Your source code, HTTP wire captures, prompts and findings are never used to train or fine-tune any AI model. Inference runs only on contracted endpoints with short or zero retention.

  4. 04Artifact retention

    30-day artifact deletion on request

    We retain only the proof needed for your report and post-patch retest. Sandbox volumes, raw captures and engagement artifacts are deleted within 30 days on request, or sooner when specified in your contract.

  5. 05Authorization gate

    Zero active testing before written RoE execution

    No active probing, scanning or exploitation begins until both parties execute a written Rules of Engagement defining in-scope staging hosts, test accounts, testing windows and emergency stop contacts.

Questions about security?

Ask for our security and data handling details before you sign.