Examples
Cybersecurity CV Examples
A security CV needs to show both breadth (frameworks, compliance) and hands-on specificity (tools, real incidents) — "cybersecurity professional" tells a recruiter neither.
On this page
- An experience bullet that shows what you actually did
- Certifications worth naming precisely
- Show scope and severity in numbers
- Skills that show real tools
- Certifications that need renewing
- Write about incidents without revealing anything confidential
- Hands-on proof: Hack The Box, TryHackMe, CTF results
- Moving into security from IT or development
- Security clearance
- These applications go through an ATS almost every time
An experience bullet that shows what you actually did
"Responsible for company cybersecurity and monitoring threats."
"Led incident response for a phishing campaign affecting 400 employees, containing the breach within 3 hours and rebuilding SIEM detection rules to catch the same pattern going forward."
Certifications worth naming precisely
CompTIA Security+, CEH, OSCP, CISSP, CISM — write them into their own Certificates section with issuer and year. Several of these expire, so PortifyCV’s expiry-date field is especially useful in this field.
Show scope and severity in numbers
Security work is easier to judge with numbers: endpoints or users monitored, alerts triaged a day, incidents handled a year, and how fast you detect and contain them (often called MTTD and MTTR). "Triaged about 200 alerts a week across 15 client networks" places you at once.
Skills that show real tools
- SIEM: Splunk, QRadar, Microsoft Sentinel
- Vulnerability management and penetration testing
- Incident response and forensic analysis
- Compliance: NIST, ISO 27001
- Identity and access management (IAM)
Certifications that need renewing
Many security certifications expire or need continuing education credits to stay valid. List each with its issuer, the year and the expiry date (PortifyCV’s Certificates section has a field for it), so a recruiter doesn’t have to check. Put the certifications the posting names first.
Write about incidents without revealing anything confidential
Describe the kind of incident, your part and the outcome, never client names, IP addresses or details that could identify a system: "Contained a ransomware outbreak at a 400-person client within 3 hours; no data was lost" is specific enough. If a description would need confidential detail to make sense, keep it general.
Hands-on proof: Hack The Box, TryHackMe, CTF results
PortifyCV’s Links section has dedicated fields for Hack The Box and TryHackMe specifically — if you have a profile on either, it belongs there as its own line, not buried in prose.
Moving into security from IT or development
Much of what a SOC or security team needs you may already do: reading logs, networking, scripting, patching, access management. Name those skills in security terms ("log analysis", "hardening", "identity and access management"), add a home lab or CTF results to show you practise, and choose the side that fits your background: IT moves often lead into defensive (blue team) work, development into application security.
Security clearance
If you hold a security clearance, say so and give its level when you’re allowed to. In Finland, many public-sector and critical-infrastructure roles require a security clearance (turvallisuusselvitys), and having one can shorten the hiring process.
These applications go through an ATS almost every time
Large companies and public-sector employers screen security applications automatically almost universally — a single-column layout with no columns or icons matters more here than in most fields.
Read the ATS-Friendly CV Guide and check your own score before you apply.
A full cybersecurity analyst CV
The same example person in two templates. Each opens as a complete CV, and "Use this example" loads it into the builder to edit.
