
We release every week. Is an annual penetration test enough?
Continuous delivery changed how often your attack surface moves. Here is how to set a testing cadence that keeps up with it.
Offensive Security
The testers who run our penetration testing engagements, writing up what they find worth explaining.

Continuous delivery changed how often your attack surface moves. Here is how to set a testing cadence that keeps up with it.
A safe, own-system method for finding out whether your API hands back more than it should, and to whom.
Set a testing cadence you can defend: by how often you change, how much risk you carry, and what your customers and regulators ask for.

A practical way to build an outside-in inventory of your own domains, subdomains and servers, and to keep it current as teams ship new things.
The difference between a scan, an assessment and a test, and how to tell which one a quote is really offering before you sign.
A closed ticket is not proof. What a proper retest checks, how to stop the issue coming back, and the evidence worth keeping.

The checks worth running before an application largely written by a coding assistant goes in front of real users and real data.
Why the same findings return between tests, and how to fix the root cause across every code path instead of the one instance a report showed.
What actually moves a penetration testing quote up or down, and how to compare two of them without guessing.

Accounts, environments, scope, contacts and windows: everything to have ready so testers spend their time testing, not waiting for access.
What each one finds, what each one asks of your team, and how they fit together in a testing programme that grows with you.
The artefacts that satisfy a reviewer asking how you know your systems were tested and your fixes landed.
Turning “test our systems” into a scope with boundaries, so the quote matches the risk you actually carry.
How to turn an unmanageable scanner backlog into a short list of things that are genuinely reachable and genuinely worth fixing first.
The family of authorisation failures behind many serious application findings, explained from the defender’s side, with no exploit detail.
What could be reached or abused in your AWS accounts, what AWS covers for you under shared responsibility, and what you have to check yourself.

How testers establish, safely and with evidence, whether a weakness can actually be used against you, and why a severity score alone cannot tell you.
An honest first check for website owners: the warning signs, the safe self-checks you can run on your own site, and when to get a test.