Skip to main content
JobDescription.orgSearch

Information Technology

Cybersecurity Engineer Job Description

A cybersecurity engineer designs, deploys and tunes the technical controls that protect an organization's networks, cloud accounts, endpoints and identities. The role sits inside the security team, usually between the security operations center that answers alerts and the infrastructure and software teams whose systems need protecting. Where an analyst works the queue, the engineer owns the tooling, the detection logic, the access model and the security review of new systems. The closest BLS occupation is information security analysts, with a May 2025 median wage of $129,180, with the 10th to 90th percentile spread running from $75,090 to $199,850.

Last updated

Role at a glance

Typical education
Bachelor's degree in computer science, information systems, cybersecurity or a related field.
Typical experience
Typically 3 to 5 years of systems, network, software or SOC experience before a mid-level engineering title.
Key certifications
CompTIA Security+, CISSP (ISC2), OSCP (OffSec), and cloud security certifications from AWS, Microsoft and Google Cloud.
Top employer types
Computer systems design firms, finance and insurance companies, corporate headquarters, and information-sector companies.
Growth outlook
BLS projects 21% growth for information security analysts from 2025 to 2035.
AI impact (through 2030)
AI tools now speed up triage and log analysis, while engineers take on validating AI output and securing AI systems.

Duties and responsibilities

  • Design security architecture for enterprise networks, cloud tenants and hybrid environments, documenting trust boundaries, data flows and the controls that enforce them.
  • Configure and maintain endpoint detection and response agents, tuning prevention policies and exclusions so protection holds without breaking business applications.
  • Build identity controls including single sign-on, phishing-resistant multifactor authentication, conditional access rules and privileged access workflows for administrators.
  • Write and test detection rules in SIEM query languages such as SPL or KQL, mapping each rule to MITRE ATT&CK techniques.
  • Automate alert enrichment, ticket creation and containment steps with Python scripts and SOAR playbooks so analysts spend time on judgment calls.
  • Review cloud configurations and infrastructure-as-code templates for overly broad IAM permissions, public storage, missing logging and unencrypted data stores.
  • Run threat modeling and security design reviews for new applications, vendor integrations and acquisitions before they reach production.
  • Manage the vulnerability remediation cycle with infrastructure owners, prioritizing fixes by exploitability, exposure and asset value and tracking each to closure.
  • Segment networks and enforce firewall and microsegmentation policy so a compromised workstation cannot reach payment systems, domain controllers or backups.
  • Evaluate security products through scoped proofs of concept, then write the standards, runbooks and handoff documentation other teams follow afterward.

Overview

A cybersecurity engineer is the builder on a security team. Analysts in the security operations center work the alert queue; the engineer decides which tools generate those alerts, how the tools connect, what they are tuned to catch and which attack paths are closed before anyone has to investigate them. The work is closer to infrastructure engineering than to monitoring, with change tickets, code reviews and maintenance windows as everyday mechanics.

The federal NICE Workforce Framework for Cybersecurity (NIST SP 800-181 Rev 1), published on CISA's NICCS site, splits this ground into separate work roles. Its Cybersecurity Architecture role is responsible for "ensuring that security requirements are adequately addressed in all aspects of enterprise architecture," and its Secure Systems Development role covers "the secure design, development, and testing of systems." A single engineering job may carry pieces of both, plus a share of tool administration.

Identity and access. An engineer might spend a quarter moving administrators onto a privileged access platform, replacing SMS codes with FIDO2 security keys for high-risk groups, and writing conditional access rules in Microsoft Entra ID or Okta that block sign-ins from unmanaged devices. Each change gets tested against real business workflows first, because an access rule that locks the finance team out on close day will not stay in place for long.

Detection engineering. The engineer writes and maintains rules in Splunk SPL, Microsoft Sentinel KQL or vendor-neutral Sigma, maps them to MITRE ATT&CK techniques, and tests them against simulated attacker behavior with tools such as Atomic Red Team. The goal is a queue analysts can trust: rules that fire on credential dumping or suspicious PowerShell, not on every scheduled backup job.

Cloud security. In AWS that means IAM policy reviews, service control policies, GuardDuty and Security Hub findings, and CloudTrail logging that cannot be switched off by a compromised account. In Azure and Google Cloud the vocabulary changes but the job is the same. Engineers who work with platform teams often add policy-as-code checks, using tools such as Checkov or Open Policy Agent, so a Terraform pull request that opens a storage bucket to the internet fails before it merges.

The rest of the week goes to design reviews and threat modeling for new applications and vendors, vulnerability remediation meetings with system owners, network segmentation changes, product evaluations, and documentation. When a serious incident lands, the engineer may be pulled in to contain it, because they know which levers the tooling actually has: isolating a host, revoking sessions, rotating keys or blocking an indicator at the edge.

Qualifications

The usual route into security engineering runs through another technical job. BLS lists a bachelor's degree as the typical entry-level education for information security analysts, the closest BLS occupation, and notes that many analysts come from an information technology department, often as a network and computer systems administrator. Engineers can arrive the same way, or from software development, cloud operations or a few years in a security operations center.

Education. A degree in computer science, computer engineering, information systems or cybersecurity is the standard starting point. Candidates without a degree can make their case with military technical training, a strong systems administration record, certifications and a portfolio of work they can show.

Experience. Plan on roughly three to five years of hands-on technical work before holding a mid-level engineering title. The experience that counts is ownership: a tool you deployed, a detection program you built, a cloud account structure you hardened, or an access model you redesigned and ran in production. Aim to build a record that goes beyond monitoring.

Credentials worth pursuing:

  • CompTIA Security+ (CompTIA), an entry-level baseline
  • GIAC Security Essentials, GSEC (GIAC)
  • Certified Information Systems Security Professional, CISSP (ISC2), a broad credential for experienced practitioners
  • Offensive Security Certified Professional, OSCP (OffSec), a hands-on exam that builds an attacker's view of defenses
  • AWS Certified Security - Specialty (Amazon Web Services)
  • Microsoft Certified: Azure Security Engineer Associate (Microsoft)
  • Google Cloud Professional Cloud Security Engineer (Google Cloud)
  • Certified Information Security Manager, CISM (ISACA), for engineers heading toward management

Technical skills. Expect to work across these areas, with depth in two or three:

  • Identity and access: Active Directory, Microsoft Entra ID, Okta, privileged access tools such as CyberArk
  • Detection and response: Splunk, Microsoft Sentinel, Elastic, CrowdStrike Falcon, Microsoft Defender for Endpoint
  • Cloud security: AWS IAM, GuardDuty and Security Hub, Azure Policy, Microsoft Defender for Cloud, Google Cloud Security Command Center
  • Application and pipeline security: static and dynamic testing, dependency and secrets scanning, the OWASP Top 10
  • Networking: TCP/IP, DNS, TLS, firewall policy, segmentation and zero trust access design
  • Code: Python for automation, PowerShell and Bash for host work, Terraform for infrastructure as code

Working style. Strong engineers write clear design documents, explain risk in terms a system owner accepts, and know when a control is good enough to ship. The job runs on persuasion as much as configuration, since the team that owns a system is the one that applies the fix. Security engineers with defense or federal clients may also need to pass a background investigation for a clearance.

Career outlook

The federal projection is strong. BLS expects employment of information security analysts, the closest BLS occupation to security engineering, to grow 21 percent from 2025 to 2035, much faster than the average for all occupations. BLS puts the employment change at 40,600 jobs on a base of 192,900 jobs in 2025, with about 14,100 openings projected each year on average. BLS attributes part of that demand to the "increased use of artificial intelligence (AI) and the rise of e-commerce," which have raised the need for security.

Employers are concentrated. According to BLS, computer systems design and related services employed 22% of the occupation, finance and insurance 17%, and management of companies and enterprises and the information sector 9% each. That places much of the work at IT services and consulting firms, banks and insurers, and corporate headquarters.

Budgets are a separate question from long-run demand. ISC2's 2025 Cybersecurity Workforce Study, a global survey of a record 16,029 cybersecurity professionals, found budget cuts reported by 36% of respondents and layoffs by 24%, each down one percentage point from the prior year. A third (33%) said their organizations lack the resources to staff their teams adequately. The same study found 41% of respondents named AI as a top skill need, followed by cloud security at 36%.

AI is changing which tasks people do by hand. ISC2's July 2026 research, based on a May 2026 survey of 856 cybersecurity professionals who use AI (ISC2 does not report results by country), found that alert triage, log analysis, report generation, vulnerability prioritization and basic threat hunting "are increasingly being performed or accelerated by AI-powered tools." Nearly two-thirds (62%) said AI has not reduced the need for foundational cybersecurity skills, against 26% who said it has. Engineering work around AI includes integrating AI assistants into the SOC stack, deciding what data those tools can reach, and securing the language-model applications the business builds, where prompt injection and data leakage have to be handled in the design.

Regulation shifts the workload by sector. For defense contractors, the Department of War announced on July 13, 2026, the immediate suspension of CMMC Phase II requirements, which had been scheduled for November 10, 2026, and said it would begin a review of the program. Phase I self-assessment requirements remain in place, and during the pause the department says it will enforce compliance with NIST 800-171 Rev 2 through self-assessments and select government-led assessments.

The usual progression runs from security engineer to senior and staff engineer, then to security architect or principal engineer on the technical track, or to security engineering manager, director and eventually CISO on the management track. Specialties with their own ladders include cloud security, application and product security, detection engineering, identity, and operational technology security.

Sample cover letter

Dear Hiring Manager,

I am applying for the Cybersecurity Engineer role on your infrastructure security team. For the past three years I have worked as a security engineer at a regional insurance carrier, and before that I spent two years as a Windows and Linux systems administrator, which is where I learned how production systems break and how to change them without breaking them.

My largest project was rebuilding our administrator access. Domain admins were signing in from their everyday laptops with standing privileges. I scoped the problem, ran a proof of concept with two privileged access vendors, and rolled out the one we chose in phases, starting with the infrastructure team and ending with our database administrators. Every privileged session now runs through a vaulted account with recording, and the old standing admin accounts are gone. I also wrote the runbooks the help desk uses for break-glass access, so the control survives when I am on vacation.

On the detection side, I own our Microsoft Sentinel content. I rewrote our noisiest rules after sitting with the SOC analysts for a week to learn which alerts they had quietly stopped reading, and I built Logic Apps playbooks that enrich every identity alert with sign-in history and device status before a human sees it. The analysts now close routine alerts faster and escalate the real ones sooner.

I hold the CISSP and the Azure Security Engineer Associate, and I am studying for the AWS security specialty because your environment runs mostly in AWS. I would welcome the chance to talk about your detection roadmap and where an engineer with an identity and Sentinel background could help first.

Thank you for your time and consideration.

Sincerely, [Your Name]

Frequently asked questions

What does a Cybersecurity Engineer do?
A cybersecurity engineer designs, deploys and tunes the technical controls that protect an organization's networks, cloud accounts, endpoints and identities. The role sits inside the security team, usually between the security operations center that answers alerts and the infrastructure and software teams whose systems need protecting. Where an analyst works the queue, the engineer owns the tooling, the detection logic, the access model and the security review of new systems. The closest BLS occupation is information security analysts, with a May 2025 median wage of $129,180, with the 10th to 90th percentile spread running from $75,090 to $199,850.
What are the main duties of a Cybersecurity Engineer?
Core duties include: design security architecture for enterprise networks, cloud tenants and hybrid environments, documenting trust boundaries, data flows and the controls that enforce them; configure and maintain endpoint detection and response agents, tuning prevention policies and exclusions so protection holds without breaking business applications; and build identity controls including single sign-on, phishing-resistant multifactor authentication, conditional access rules and privileged access workflows for administrators.
How is a Cybersecurity Engineer different from a cybersecurity analyst?
An analyst investigates alerts, scopes incidents and reports on risk using the tools already in place. A cybersecurity engineer builds and tunes those tools: the detection rules, the identity system, the cloud guardrails and the automation behind the alert queue. On a small team one person may do both jobs.
What does zero trust mean for a Cybersecurity Engineer?
Zero trust drops the assumption that anything inside the network perimeter is safe, so every access request is authenticated, authorized and checked against device and context first. For the engineer that means identity-aware proxies, conditional access rules, microsegmentation between workloads and short-lived credentials for administrators, rolled out system by system.
Which programming skills matter most for security engineering?
Python covers most automation: API integrations between security tools, log parsing and enrichment scripts. PowerShell and Bash handle host-level work on Windows and Linux, and Terraform or CloudFormation matter wherever cloud infrastructure is defined as code. Engineers in application security also need to read the languages their developers write.
How is AI changing cybersecurity engineering work?
In a May 2026 ISC2 survey of 856 security professionals who use AI, which does not report results by country, 65% said they now spend more time deciding when to trust or act on AI-generated recommendations and 63% more time reviewing or validating AI outputs. Some 80% rated knowing when to override or ignore AI recommendations as very important, which puts verification and governance on the engineer's task list.
Is a security clearance useful for this career?
Positions that touch classified systems at defense contractors and federal agencies require a clearance, which the government grants after a background investigation tied to a sponsoring employer. A candidate who already holds an active clearance can start that kind of work without waiting on a new investigation.

Sources

Salary figures and role details on this page were checked against the following sources. Dates show when each was last reviewed.

  1. Information Security Analysts, BLS Occupational Employment and Wage Statistics (May 2025)Checked Nov 2, 2026
  2. Information Security Analysts, Occupational Outlook Handbook, U.S. Bureau of Labor Statistics (2026)Checked Nov 2, 2026
  3. ISC2 Study: Budget Constraints Remain, Skill Needs Grow (2025 Cybersecurity Workforce Study), ISC2 (December 4, 2025)Checked Nov 2, 2026
  4. ISC2 Research: Rethinking AI's Impact on Cybersecurity Roles, ISC2 (July 14, 2026)Checked Nov 2, 2026
  5. Cybersecurity Architecture, NICE Framework Work Role, CISA NICCS (2026)Checked Nov 2, 2026
  6. Secure Systems Development, NICE Framework Work Role, CISA NICCS (2026)Checked Nov 2, 2026
  7. Forging the Arsenal of Freedom: Department of War Suspends CMMC Phase II Requirements, U.S. Department of War (July 13, 2026)Checked Nov 2, 2026
  8. Security+ Certification, CompTIAChecked Nov 2, 2026
  9. CISSP Certified Information Systems Security Professional, ISC2Checked Nov 2, 2026
  10. PEN-200 and the OSCP Certification, OffSecChecked Nov 2, 2026
  11. GIAC Security Essentials (GSEC), GIACChecked Nov 2, 2026
  12. CIO memorandum on the CMMC Phase II suspension, Attachment 1: Cybersecurity Maturity Model Certification Procedures, Department of War (July 13, 2026)Checked Nov 2, 2026