Map Your Security Role Shift With the 2026 Workforce Report

Your security job may not be disappearing. It may be moving, and the 2026 SANS | GIAC Cybersecurity Workforce Report gives you a map of where the pressure is landing. Use it to decide whether to stay in your current lane or move into an AI security role. The report reflected input from nearly 1,000 practitioners, leaders, and HR professionals in six regions worldwide.

The bigger workforce problem is skills, not headcount. 60% of organizations said skills gaps were the greater workforce problem versus 40% for staffing shortages, a 20-point gap that had been only four points a year earlier. At the same time, 74% of organizations said AI was already affecting cybersecurity team size or role structures.

The shrinking side is the one to watch first

SOC/security analyst cuts were 32%, threat-intelligence analyst cuts were 26%, and incident-responder cuts were 22%. If your work centers on routine monitoring, triage, or first-pass response, that is the part of the map that should make you uncomfortable. Treat it as a signal that those tasks are being compressed, not as a guarantee that every analyst seat will vanish. List the work you can do after the alert, not just the alerts you can watch.

The opening side is where your next role lives

Among organizations adding roles, 34% had AI/ML security specialists, 32% had added AI security engineers, and 30% had AI governance analysts. Job platforms had over 2,500 active AI/ML security engineer postings as of March 21, a role category that was nearly absent three years earlier. Those openings are where existing security instincts can be priced higher, if you can show the technical work behind them.

AI security engineer jobs are the clearest opening, but they are not a license to quit your current lane. The market rewards people who can secure AI, not just people who can say it. Attach a sample of that work to your next conversation, and let your resume show the same proof.

Build the skill bridge before the market does it for you

Technical capability led all hiring criteria at 55%, ahead of work experience at 46%. Do not chase a badge because it sounds current. Build proof that you can inspect, test, and explain AI systems under pressure. Incident responders have an edge: knowing how a model failure becomes a breach, and how you contain it. Start from your current work and add a new attack surface to it, rather than treating AI security as a separate discipline you must enter from zero.

This week is when the role shift starts

• Map your exposure. Put your current role on the left, the shrinking category it sits in, and the opening role you want on the right. Name the skills that connect them. Keep it to the roles you can realistically reach in the next hiring cycle. You are done when you can show a short document to a manager, a recruiter, or yourself without explaining the context.
• Choose the target role. Pick an opening category, not several. Aim for AI security engineering if your background is engineering, AI governance analysis if it is policy, or AI/ML security specialization if it is operations. A finished version is a sentence you can say out loud: I am moving from X to Y because I can already do Z.
• Build proof. Pick an artifact you can finish this week: a write-up of an AI-related incident, a model-risk checklist, a governance note for a tool your team uses, or a small test of an AI feature in a sandbox. The finish line is a document that shows you can inspect, test, and explain the system, not merely name it.
• Ask for the stretch. Tell your manager you want an AI security task in the next cycle. If you cannot get it internally, ask a peer in another team for a brief walkthrough of their AI risk work. You will know it is ready when you have a calendar invite or a shared doc, not a vague intention.
• Tell a person. Send your role-shift map to a hiring contact, a mentor, or a manager. Ask for a correction. A finished reply says what is missing, what is credible, and what you should do next.