惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
月光博客
月光博客
MyScale Blog
MyScale Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
爱范儿
爱范儿
P
Proofpoint News Feed
人人都是产品经理
人人都是产品经理
Last Week in AI
Last Week in AI
罗磊的独立博客
G
Google Developers Blog
Y
Y Combinator Blog
博客园 - 【当耐特】
WordPress大学
WordPress大学
大猫的无限游戏
大猫的无限游戏
博客园 - 叶小钗
J
Java Code Geeks
酷 壳 – CoolShell
酷 壳 – CoolShell
V
Visual Studio Blog
美团技术团队
宝玉的分享
宝玉的分享
Jina AI
Jina AI
小众软件
小众软件
T
Tailwind CSS Blog
A
About on SuperTechFans

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
SLE, ARO, ALE: the Security+ risk math that looks easy un...
TiltedLunar123 · 2026-06-16 · via DEV Community

Most people studying for SY0-701 can recite the quantitative risk formulas in their sleep. Then the exam hands them a word problem where the frequency is phrased as "once every four years" instead of a clean decimal, and half the room writes down a different answer. The math is not hard. The wording is where points leak out.

Here is the whole chain, in order, with no shortcuts.

The five values, in the order they build on each other

AV (Asset Value) is what the thing is worth. A server, a database, a building. Say a customer database is valued at $200,000.

EF (Exposure Factor) is the percentage of that value you lose in one bad event. Not every incident destroys the whole asset. A ransomware hit might cost you 40 percent of the database's value in downtime, recovery, and lost records. EF is 0.40.

SLE (Single Loss Expectancy) is the dollar cost of one event:

SLE = AV x EF
SLE = $200,000 x 0.40 = $80,000

ARO (Annualized Rate of Occurrence) is how many times per year you expect the event. This is the one that bites people. "Twice a year" is 2. "Once every four years" is not 4. It is 1 divided by 4, which is 0.25.

ALE (Annualized Loss Expectancy) is what you expect to lose per year:

ALE = SLE x ARO
ALE = $80,000 x 0.25 = $20,000

That $20,000 is the number a security program actually budgets against. It answers "how much is this risk costing us per year, on average."

Where the points actually leak

Inverting ARO. When the question says "once every five years," the rate is 0.2, not 5. Read the sentence twice. If the event is rare, ARO is a fraction. If it happens several times a year, ARO is a whole number bigger than one.

Stopping at SLE. A question gives you AV, EF, and a frequency, then asks for annual loss. If you answer with SLE you answered a different question. Annual means you multiply by ARO. Every time.

EF as a percent vs a decimal. Forty percent is 0.40 in the formula. Plugging in 40 inflates your SLE by a factor of one hundred, and the answer will not match any option, which is at least a useful signal that you slipped.

The cost-benefit trap. The exam loves to follow the math with a proposed control that costs some amount per year, then ask whether it is worth deploying. The rule is simple: if the annual cost of the control is less than the reduction in ALE, it is justified. If a control costs $25,000 per year but only drops your ALE from $20,000 to $12,000, you spent $25,000 to save $8,000. That is a bad trade, and the question wants you to say so.

A second pass, because repetition is the point

A warehouse is valued at $1,000,000. A fire would destroy an estimated 25 percent of it. Records suggest a fire of that size every ten years. Find the ALE.

EF  = 0.25
SLE = $1,000,000 x 0.25 = $250,000
ARO = 1 / 10 = 0.1
ALE = $250,000 x 0.1 = $25,000

If you got $250,000 you forgot to annualize. If you got $2,500,000 you multiplied by 10 instead of 0.1. Both are the exact mistakes the distractor answers are built from.

How this shows up on test day

SY0-701 puts this in the risk management material (Domain 5), and it can appear as a straight calculation or buried inside a performance-based question where you have to pick the justified control. You will not get a calculator surprise: the numbers are usually clean once you set ARO correctly. The skill being tested is whether you can read a sentence, assign each number to the right letter, and not stop one step early.

The fastest way to make this automatic is to grind a handful of these with different phrasings until the "once every N years means 1/N" move is reflex. Mixed practice beats re-reading the formula sheet, because the formula was never the hard part.

If you want to see where you actually stand on this and the rest of the objectives, there is a free diagnostic at secplusmastery.com/diagnostic that maps your weak spots to specific domains, and the question bank on secplusmastery.com has plenty of these risk problems with worked solutions if you want to drill them.

One last sanity check you can carry into the exam: ALE is a per-year number, and it should be smaller than SLE unless the event happens more than once a year. If your ALE comes out larger than your SLE and the event is rare, you inverted ARO. Catch that and you have caught the single most common mistake on this topic.