Frontier Investigationfor Offensive Security

Every finding on your apps and APIs backed by proof, with the fix attached.

A yearly security test looks at your apps for one week of the year. Agents test the web apps and APIs you own on the schedule you set, on domains you have verified. Every verified finding carries the request and response that prove it, and arrives with the fix drafted as a pull request.

  • Cloud accounts
  • Edge, CDN
  • Public APIs
  • Cloud findings
  • CNAPP
  • Code scanning
  • Git repos
  • Tickets
  • CloudThinker Cyber
  • Test runs
  • Approvals
Existing systemsNew with CloudThinkerRead-only connection

The work behind every finding

Your apps change with every release.Your security test happens once a year.

01The manual work

Test

A scanner report is only the start. AppSec still decides what is reachable, reproduces it by hand and argues about severity.

02The agent handoff

Verified

Frontier agents test the app inside your scope, back each finding with request and response proof and draft the fix.

03Your engineers’ role

Approve

Set the scope and the intensity. Review the proof, merge the fix and confirm the retest.

Where CloudThinker fits

Your stack stays.Agents work inside it.

01What you own

Apps and APIs on your domains

  • AWSAWSApps behind your load balancers
  • AzureAzureApp Service apps
  • Google CloudGoogle CloudApps behind your load balancers
  • CloudflareCloudflareDomains and edge routes
  • Public APIYour documented endpoints

Verified domains only

02Known findings

Your system of record

  • AWSAmazon InspectorKnown CVEs
  • WizCloud posture findings, over MCP
  • SnykCode and dependency findings, over MCP
  • SemgrepStatic analysis results

No change to scanning

03Security testing

CloudThinkerCloudThinker

  • TestRoutes and endpoints tested inside your scope
  • VerifyRequest and response proof per finding
  • SeparateUnproven leads kept apart
  • FixPull request drafted for the owner

Inside your scope and intensity

04Response

Proof, not lists

  • JiraFinding and proof copied to a ticket
  • GitHubGitHubPull request for the fix
  • SlackSlackCyber alerts in the AppSec channel
  • RetestProof replayed after the fix

Fix verified by retest

Logos show common stacks. CloudThinker connects to each one through read-only access you approve.

Example scenario

Monday, 10:05. A new API version ships.The next security review is in five months.

A 120-engineer B2B SaaS company with a public API, three AWS accounts and a two-person AppSec team. Enterprise customers ask for proof of testing every quarter.

  1. 10:05

    New endpoints go liveSignal

    API v2 deploys with 9 new endpoints and an updated OpenAPI spec. AppSec starts a Cyber run on the verified API domain.

  2. 10:07

    Agent maps the changeAgent

    Reads the API docs, keeps to the include paths and runs a Safe test, read requests only, as two test users.

  3. 10:18

    One finding verifiedAgent

    Test user B can read test user A’s invoices on /v2/invoices/{id}. The request and response are saved as proof, with tokens replaced by placeholders.

  4. 10:18

    Eight passAgent

    The other 8 endpoints enforce ownership in this run, so no finding is raised for them.

  5. 10:20

    Fix draftedAgent

    The agent drafts a pull request that adds the ownership check to InvoiceController, with a regression test.

  6. 11:02

    Fixed and retestedYour team

    AppSec merges the fix, it ships at 10:55, and replaying the proof at 11:02 confirms it is fixed.

#appsec-findings4 messages
  • CloudThinker10:18

    Confirmed: broken object level authorization on GET /v2/invoices/{id}. Test user B read an invoice owned by test user A. Severity high. 8 other new endpoints passed.

  • AppSec engineer10:31

    Reproduced it on staging. Merging the PR, please retest after deploy.

  • GitHub Actions10:55

    Deploy api v2.0.1 to production succeeded.

  • CloudThinker11:02

    Proof replayed. Test user B now gets 404 on test user A’s invoices. Finding marked verified fixed, evidence kept for the quarterly report.

from deploy to verified finding
13 min
from deploy to verified fix
57 min
new endpoints passed the test
8 of 9

An illustrative example. Team, systems and times are representative, not a specific customer.

Frontier investigation agents

Every release gets tested.Only verified findings reach your team.

Agents test inside the scope you set, so a finding arrives with request and response proof, and your team fixes what is verified, not what is theoretical.

Map the app
Routes, forms and API endpoints explored on each run, kept inside your include and exclude paths.
Verify every finding
A confirmed finding is one Cyber reproduced, with the requests and responses behind it. Unproven leads stay marked as leads.
Draft the fix
Verified findings come with a pull request drafted on the attached repository. A person reviews and merges it.
Retest and report
Every fix retested by replaying the proof, with a PDF report for customers and auditors.

What changes

Same team. Same tools.Far less of the work by hand.

How often you test
TodayOnce or twice a yearWith frontier agentsDaily, weekly or on the schedule you set
Scanner findings
TodayTriaged by hand, argued overWith frontier agentsVerified with request and response proof
Fixing
TodayA PDF report for developers to readWith frontier agentsA pull request with a regression test
Retesting
TodayAt the next engagementWith frontier agentsProof replayed once the fix ships
Evidence for customers
TodayLast year’s test letterWith frontier agentsA current record of what was tested and fixed

Integrations

Connects to the rest of your stack.Read-only to start.

  • Amazon Inspector
  • AWS Security Hub
  • Amazon GuardDuty
  • Semgrep
  • GitHub
  • GitLab
  • Jira
  • Slack
  • Wiz via MCP
  • Snyk via MCP

Adoption path

One pilot.Then company-wide.

The rollout follows the four phases of the AWS Cloud Adoption Framework, so it fits the plan your cloud team already runs.

  1. 01Envision

    Agree the scope

    Pick one application, verify its domain with a DNS record, and set the include paths and test users.

  2. 02Align

    Pick the intensity

    Start with Safe, which sends read requests only. Point higher intensities at staging once scope and logins check out.

  3. 03Launch

    Add applications

    Bring each application into scope on the same rules, so every team gets the same proof format.

  4. 04Scale

    Test on a schedule

    Schedule runs daily or weekly, and let Code Audit follow the branch on every push. Findings feed threat models and secure coding training.

Trust and control

Agents do the work.Your team keeps control.

Approval by policy
Agents propose. You decide what runs on its own and what waits for approval, and a short list of destructive calls never runs.
On the record
Every check and action stays in the investigation, with who approved it. Org-wide audit logs come with Scale and Enterprise.
Independently audited
SOC 2 Type II report available in our Trust Center. ISO/IEC 42001 audit in progress.Visit the Trust Center
Runs where you need it
SaaS today, also through AWS Marketplace. Dedicated and self-hosted deployments are in early access.

Questions

What teams askbefore they start.

Is it safe to test production?
Start with Safe intensity, which sends read requests only. Higher intensities create or change test data, so point them at staging with test accounts. Runs are blocked until you verify the domain, stay inside your include paths, and you can stop one at any time.
Does this replace our yearly pentest?
No. It covers the days in between. Keep your human-led engagement for depth and compliance, and run Cyber on a schedule between them.
How is this different from a scanner?
A scanner lists what might be wrong. Cyber reproduces it against your running app inside your scope, and a confirmed finding carries the requests and responses behind it, plus a drafted fix.
What about our cloud provider’s testing policy?
DNS proof shows you control the domain, not that you may test the hosting under it. Check your provider’s security testing policy (AWS publishes one) and get written approval for third-party assets.

Test the apps you own, all year.Fix only what is verified.

Start with one application on a verified domain. See which findings agents verify before you widen the scope.

  • A CloudThinker team member holding a card reading "up to $200K active AWS credits"

    Up to $200K in AWS credits

    Applied to your own AWS account.

  • A CloudThinker team member presenting the AWS Partner AI Services Competency badge for Agentic AI Consulting Services

    AWS AI Services Competency

    Validated for Agentic AI Consulting.

  • An engineer approving a request beside a global operations map, an uptime dial, and GDPR and SOC compliance marks

    Covered 24/7, inside your policy

    With a SOC 2 Type II report.