Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Security posture is the overall state of an organisation’s defences at a point in time: what you own, how exposed it is, which controls work, and how fast you can respond.

What Is Security Posture?
Security posture is the honest answer to a board-level question: how well protected are we, right now? It combines what you own, how much of it is exposed, which controls are genuinely operating, how quickly you would notice an attack, and how well you would cope with one. The phrase is used loosely by vendors, so it helps to pin down what it is made of before trying to measure it.
Posture reporting goes wrong when it counts activity instead of outcomes. The number of alerts triaged or patches deployed says nothing about whether the organisation is harder to compromise. A small set of outcome metrics works better.
| Metric | What it tells you |
|---|---|
| Percentage of assets in the inventory with an owner | Whether anyone can be asked to fix a problem |
| Mean time to remediate critical internet-facing vulnerabilities | How long your worst exposure stays open |
| Multi-factor authentication coverage on privileged accounts | Resistance to the most common initial access route |
| Mean time to detect and mean time to contain | Whether detection beats attacker dwell time |
| Proportion of backups restored successfully in a test | Whether recovery is real |
| Number of accepted risks past their review date | Whether governance is keeping up |
Trend matters more than the absolute figure. A single number—whether from a security rating service or an internal scorecard—is useful for direction of travel and dangerous as a target, because scores are easy to game and external ratings see only what is visible from outside.
Self-invented scorecards are hard to defend. UK organisations generally anchor posture assessment to one of these:
None of them measures posture by itself. They give you a structure so that the gaps you report are gaps against something recognised.
Cloud security posture management scans cloud configuration against benchmarks. Application security posture management correlates findings across code and pipeline tools. Breach and attack simulation replays techniques to see whether controls block or alert. External attack surface management watches what is exposed from the internet. Each covers one slice; stitched together without an asset inventory they produce overlapping dashboards and no answer.
Periodic adversarial testing remains the sharpest instrument, because it measures the whole chain rather than individual controls. A penetration test answers whether a specific system can be broken; a red team exercise answers whether you would notice. At Privia Security, our Red Team Services are built to produce that second answer, and the findings tend to reshape a posture report more than any dashboard does.
Posture describes your current state of protection, including exposure and control effectiveness at this moment. Maturity describes how well your processes are defined, repeatable, and improving over time. An organisation can have a mature governance programme and a weak posture because a recent acquisition brought unmanaged systems, or a decent posture held together by individual effort rather than process.
Continuously for the measurable parts—asset discovery, exposure, patch status, and control coverage should be reported monthly from live data. Deeper assessments such as penetration testing, red team exercises, and framework reviews are usually annual, plus after any major change: a migration, an acquisition, a new internet-facing service, or a significant incident.
They are a useful outside-in signal and a poor summary. Rating services see externally observable evidence such as certificates, exposed services, and leaked credentials, which correlates loosely with internal reality. They cannot see your segmentation, privileged access controls, or detection capability. Treat a rating as one input, particularly for assessing suppliers, not as a measure of your own posture.
Three things: a short set of trended outcome metrics, the top risks with their current treatment status and owners, and what changed since the last report. Avoid raw tool output and activity counts. Boards need to know whether exposure is rising or falling, what decisions are needed from them, and which risks they are currently accepting.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.