EPB Bullet Examples for Cyber Airmen: Translating Technical Work
Weak and strong EPB examples for 1D7 and 1B4 cyber Airmen in each Major Performance Area, written to the AFI 36-2406 rules on rankings and acronyms.
SrA Park has been working defensive cyber operations for eight months. She found a way an attacker could have moved between 340 workstations, wrote the fix, and trained her whole work center on the new procedure. Her EPB is due in two weeks.
What her supervisor has so far: "Conducted cybersecurity operations to ensure network integrity and availability."
That one sentence is how good work gets buried.
Cyber jobs have an evaluation problem. When you stop a breach, nothing happens, and nothing is hard to count. The vocabulary that matters in your work (mean time to repair, vulnerability severity, patch compliance, alert quality) doesn't map cleanly to EPB language. Some of the work is classified, and none of that can go on the EPB.
This guide is for 1D7X1 Cyber Defense Operations and 1B4X1 Cyber Warfare Operations Airmen, and anyone else whose job is networks or systems. The 1D7 Cyber Defense Operations AFSC replaced the 3D cyber support AFSCs on 1 November 2021, so if a guide still says 3D0 or 3D1, it's old.
People still call EPB lines "bullets." The current form calls them performance statements. AFI 36-2406, Officer and Enlisted Evaluation Systems (22 August 2025), defines one as a standalone sentence that names what the Airman did and the result. The rater writes the duty description and at least one statement in each of the four Major Performance Areas: Executing the Mission, Leading People, Managing Resources and Improving the Unit. For the full layout, the ALQs under each area and the HLR section, read our Air Force EPB performance area walkthrough. This post sticks to cyber examples.
Two rules that hit cyber EPBs hardest
Classification. Paragraph 1.3.2 says no classified information goes in any part of an evaluation. If an entry would release classified information, the AFI says to write "Data Masked" in its place. Write at the level of the outcome: how many systems, how fast, what it prevented. Leave out the details of how.
Acronyms. Paragraph 1.3.6.2 says to limit acronyms, and to use only the ones on the Air Force acronym list that AFPC publishes. The duty description instructions also say to avoid jargon. A statement full of tool names and protocol abbreviations may need rewriting before it can route. Check the list. If a term isn't on it, spell it out or describe what it does. The examples below are written that way.
Why cyber statements go flat
Cyber Airmen write about activities instead of outcomes.
"Monitored network traffic" is an activity. "Caught and blocked 3 unauthorized access attempts on the unit's network before any data left it" is an outcome.
"Responded to cybersecurity incidents" is an activity. "Locked 2 compromised accounts within 40 minutes of a phishing report and reset passwords for the 85 users who had clicked the link" is an outcome.
Push past the activity and write the outcome. Then write the impact on something your rater cares about: mission availability, people trained, money saved, hours recovered. If you're not sure how to find those numbers, the quantification guide covers ways to measure scope and downstream effects.
Duty description
Weak:
Performs duties as a cyber systems technician; responsible for maintaining and troubleshooting network equipment.
Strong:
Sole Cyber Defense Operations Airman at a 22-person geographically separated unit. Maintains classified and unclassified network service for 340 users in 4 buildings supporting 3 joint mission partners.
"Sole" tells the reader the scope of the job without comparing the Airman to anyone. User counts, network types and who depends on the work raise the stakes of every statement that follows. If you can source the dollar value of the equipment you maintain from the unit's inventory, add it.
Executing the Mission
Weak:
Excellent technician; detected and responded to multiple cybersecurity incidents.
Strong:
Isolated malware on 6 unclassified workstations within 2 hours of the first alert, keeping it off the other 334 computers and avoiding a unit-wide network shutdown.
The strong version has a count, a time and the bad outcome it prevented. "Multiple incidents" gives the reader nothing to weigh.
Leading People
For cyber Airmen, the strongest Leading People material is usually teaching a technical skill or running an incident response.
Weak:
Strong leader; mentors junior Airmen on cyber operations and assists supervisors when needed.
Strong:
Taught a 4-block network defense course to 8 Airmen new to the work center; all 8 qualified on their core tasks in 60 days, half the previous timeline.
Led a 3-Airman team through an 11-hour incident investigation, briefing the commander every 2 hours until the 2 affected workstations were rebuilt and back online.
The first statement shows training with a measured result. The second shows communication, one of the three Leading People ALQs, under pressure.
Managing Resources
Stewardship covers time and money as well as equipment. Accountability covers owning what went wrong.
Weak:
Effectively managed network resources and software accounts.
Strong:
Audited 610 software licenses, found 140 assigned to departed users and cancelled the renewals, saving $23K a year.
Owned a missed security certificate renewal that took the unit's public website down for 4 hours; built an expiration tracker for all 38 of the unit's certificates, and none have lapsed in the 9 months since.
The second statement admits a failure, and that's the point. The AFI defines Accountability to include transparency, and fixing the process for every certificate is what earns it a place on the EPB.
Improving the Unit
Weak:
Innovative technician who continually improves work center processes.
Strong:
Replaced a manual patch spreadsheet with an automated compliance report, bringing 647 overdue patches to full compliance in 3 weeks and saving 28 hours a month of tracking; the wing adopted the report.
Traced 4,000 false alerts a week to 1 misconfigured firewall rule and rewrote it with the network team, giving analysts back 18 hours a week for threat hunting.
Both statements name the change and what the unit got back.
Certifications and the old Whole Airman block
Older guides told cyber Airmen to put certifications in the Whole Airman Concept block. That block no longer exists. A certification still belongs on the EPB when it changed what you could do for the unit:
Earned the CompTIA Cybersecurity Analyst certification and took over the unit's weekly vulnerability scans from an outside team, clearing a 3-week scan backlog in 5 days.
The certification name is written out in full instead of its short form (CySA+), so it doesn't run into the acronym rule.
Leave out comparisons like "only Airman in the work center to hold both certifications." Paragraph 1.12.7 prohibits test scores and relative standings among peers.
No rankings, including by career field
Old cyber EPB examples often opened with "#1 of 7 SrA in the unit" or an award won "1 of 3 MAJCOM-wide." Neither belongs in a performance statement, and below MSgt there is no stratification block at all. Paragraph 4.11.1.3 prohibits stratification by anyone other than the senior rater, including implied stratifications. It also bans stratifications based on career field or functional community, so "best 1D7 in the group" is out too. Paragraph 1.12.11 bans stratifications based on awards. You can say the Airman won the award; you can't rank them by it.
Turning everyday tasks into performance statements
Most cyber work runs on a ticket queue: patches, scans, outages, certificate renewals. None of it makes headlines on its own, but all of it produces numbers if you count what you touched.
| Everyday task | Performance statement |
|---|---|
| Ran a vulnerability scan | Found 23 critical vulnerabilities across the unit's network and patched all of them within 72 hours, cutting the median time a vulnerability stayed open from 22 days to 8. |
| Fixed a recurring network outage | Traced a recurring routing outage to a misconfigured timer and fixed it, ending 11 monthly outages that averaged 45 minutes each. |
| Worked the help desk queue | Closed 312 trouble tickets in 90 days, resolving 97% within the unit's response standard. |
| Set up new users | Built and configured 120 workstations for a new squadron in 9 days, so every user was online before the squadron's first day of operations. |
| Ran a security configuration review | Reviewed security settings on 14 systems and closed 47 open findings, including 2 high-severity ones, keeping the unit's authorization to operate on schedule. |
Every row follows the same pattern: the task, a count, the outcome and the impact.
One test before it routes
Read the draft out loud. Any phrase that could appear word for word on another cyber Airman's EPB needs more detail. "Maintained network security posture" fits every cyber EPB in the Air Force. "Cut the median time a vulnerability stayed open from 22 days to 8 across 340 computers" only fits one.
If you're the ratee, send your supervisor those facts and numbers, not a finished EPB. Paragraph 1.6.3.6 encourages inputs but says no one can direct a ratee to write their own evaluation.
RapidEPR's bullet tool handles the translation step for raters. Drop in the raw version of what the Airman did, jargon included, pick the EPB Section (Enlisted) format and the section, and get a draft performance statement back. Check it against your facts, the acronym list and the AFI before you route it.
Write your next bullet in seconds.
RapidEPR turns your accomplishments into branch-perfect EPB, OPB, NCOER, OER, EVAL, FITREP, EER, and award bullets in seconds.