About Services Tools Blog Contact us

Application Security Audit

A structured review of a web application that writes up the likely threats and keeps only the findings it is confident about.

  • Security & Hosting
  • Cross-sector
  • Agent skill
  • Productised
  • Local/private
  • 2026

The problem

Security reviews tend to become a long checklist nobody reads, or they never happen. Meanwhile leaked passwords and keys, weak links to other services and risky add-ons sit in the code until something goes wrong.

What it does

Someone gives it the application source and picks daily or monthly mode. It starts from how the system is built and where it can be attacked, then checks for stored passwords and keys, third-party code, the publishing process and links to other services. A daily pass keeps only high-confidence issues. A monthly pass accepts lower confidence and records a trend.

Outcomes

  • A short findings list replaces an unread checklist.
  • A written threat model is saved for the team to keep.
  • A monthly trend shows whether risk is rising or falling.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

lane-checkout

Files
0
Kept
0
Deferred
0
Stack
PHP shop

186 files · daily pass 10 October 2026, 07:40 · sample tree, not a live shop

Sample environment file Kept

config/sample.env:14

A payments secret is still in a file meant to be a sample. The value matches a live-key shape: sample-key-7f3a.

Confidence 0.91 Clears the daily gate
Unsigned payment callback Kept

public/hooks/payment.php

The callback marks an order paid without checking a signature on the body.

Confidence 0.86 Clears the daily gate
Re-apply the daily gate
Gate 0.80 · noisy notes stay off the list

Threat model

Monthly · 1 October

Written on the monthly pass and kept for the team. Four trust boundaries, not a checklist.

01 Shopper browser Catalogue, basket and session cookie. Untrusted input starts here.
02 Payment callback A card provider posts the result. Today the body is trusted with no signature.
03 Staff admin Orders and refunds. Its login is not the shopper session.
04 Supplier drop A product file arrives on a schedule. The worker reads it and does not run it.
What changed since March

The supplier drop was inside the shop process in March. It is now its own worker. The unsigned callback is the boundary that did not move.

Kept findings

High-confidence items still open

Down from 9 in May to 2 this morning. The October bar is the daily pass.

PassModeKeptDeferredNote
1 MayMonthly96First written model
1 AugustMonthly65Supplier drop split out
1 OctoberMonthly43Image helper first noted
10 OctoberDaily21Gate 0.80, helper deferred

How it works

  1. Read how the system is built and list where it can be attacked.
  2. Search for exposed secrets, risky third-party code and weak points in the publishing process.
  3. Review links to other services and the common ways web applications fail.
  4. Keep a finding only when it meets the confidence level for that run.
  5. Write a short threat summary and, monthly, compare it with the previous one.

Pipeline

flowchart LR
  A[Source tree] --> B[Attack surface]
  B --> C[Secrets and dependencies]
  C --> D[Webhooks and integrations]
  D --> E{Confidence gate}
  E -->|Keep| F[Findings]
  F --> G[Threat model]