> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opsbeacon.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Security Trade-off Score

> A single score that quantifies the financial trade-off between your security posture and the cost to fix it.

## What the score measures

The Security Trade-off Score (0–100) reflects how well your security investment is aligned with your actual risk exposure. A low score means you have high-cost security gaps that are cheap to fix. A high score means your security investment is proportional to your risk.

The score factors in:

* Total monthly dollar exposure from open security gaps
* Estimated cost and effort to remediate each gap
* Number of high-severity findings vs total findings
* Time since findings were first detected

## How to get your score

```
@Beacon run security economics report
@Beacon what's my security trade-off score?
```

## What a good score looks like

| Score | Interpretation |
| - | - |
| 80–100 | Strong posture — gaps are minor or expensive to fix relative to risk |
| 60–79 | Manageable — a few high-value fixes available |
| 40–59 | Attention needed — meaningful exposure at low remediation cost |
| 0–39 | Critical — significant risk with available fixes being deferred |

## Improving your score

The fastest way to improve the score is to resolve high-exposure, low-effort findings first. Beacon surfaces these as **Priority Actions** in the Security Economics Report.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.