Career Change to Cybersecurity: How to Get Started
Most people move into security sideways from IT, audit, the military or support work, and this guide covers how that path actually runs.
By Marcus Lee · Published · Updated · 14 min read

You get into cybersecurity by picking one entry-level role, proving the fundamentals with a recognised certification, and building a small pile of hands-on evidence an employer can check. Almost nobody starts in "hacking" — the usual doors are a security operations centre, identity and access administration, or a governance and compliance desk.
From a standing start, expect 9 to 18 months of part-time study and applications. If you already work in IT support, networking or internal audit, it can be a lot shorter, because half the job is already on your CV.
Is it right for you? (checklist)
Answer these honestly. They are about the work as it is done day to day, not about how it looks from outside.
- Are you comfortable reading logs, tickets and policy documents for hours? Much of security is pattern-reading and writing things down. The dramatic incidents are rare and the paperwork afterwards is not.
- Can you work shifts, nights or on-call if the role requires it? Monitoring roles in a 24/7 operations centre often run rotating shifts. Compliance and engineering roles usually do not. Decide which you can live with before you apply.
- Do you learn technical things without a teacher in the room? Security changes constantly. Nobody will hand you a syllabus after you are hired. If you need structured teaching to learn anything, factor in a college programme rather than self-study.
- Are you willing to study for a certification exam while holding down your current job? Most changers do their first exam in evenings and weekends over two to four months.
- Can you explain a technical problem to somebody who does not care about it? You will tell a finance manager why their file share is being locked down. Persuasion is a bigger part of the job than most people expect.
- Do you accept that you may start below your current level of seniority? A mid-career manager moving across often enters as an analyst, reporting to somebody younger.
- Are you prepared to apply for months without a response? Entry-level security postings attract very large numbers of applicants, including career changers with the same certification you have.
If you answered yes to five or more, the fit is plausible. If you said no to the last two, stop and look at security-adjacent work instead — IT support, systems administration or internal audit — where the entry bar is lower and the route into security opens from inside.
The honest downside: the first job is the hard one. Certifications get you past automated screening, not past a hiring manager who wants evidence you have touched the tools. People who stall are almost always the people who studied for an exam and did nothing hands-on.
What transfers (table)
Security teams hire from support desks, audit departments, the military and classrooms far more often than from nowhere. Work out what you already have before you spend money on training.
| Skill from your current role | How it applies in cybersecurity |
|---|---|
| Helpdesk or IT support troubleshooting | Triaging security alerts is the same loop: gather facts, form a hypothesis, test, escalate. Ticketing and queue discipline transfer directly to a security operations centre. |
| Internal audit, accounting or compliance work | Governance, risk and compliance roles run on evidence collection, control testing and framework mapping. You already know how to chase people for documentation. |
| Military, policing or emergency services | Clearance eligibility, incident discipline, chain of custody, calm under escalation, and working to standard operating procedures during an incident. |
| Teaching or training | Security awareness programmes, phishing simulation follow-up, and explaining a policy change to a department that resents it. |
| Project or programme management | Running remediation projects, patching campaigns and audit readiness work, where the obstacle is coordination rather than technology. |
| Software development | Application security review, secure code practice, writing automation scripts, and understanding what developers will and will not accept. |
| Customer service or claims handling | Writing clear incident notes, de-escalating with an angry user whose account you just disabled, and sticking to a process under pressure. |
| Healthcare, legal or finance admin | Sector knowledge of regulated data handling, which makes you useful to a security team working in that same sector. |
Two cautions. First, transferable does not mean interchangeable — you still need the technical fundamentals of networking, operating systems and identity. Second, you must translate this on paper. "Handled escalations" means nothing to a security hiring manager; "triaged 40 tickets a day, escalated account compromise cases to the IT manager" does.
Roles to aim for (table)
Pick one and aim everything at it. Applying to "cybersecurity" generally produces a scattered CV that suits no posting.
| Role | Usual entry requirement | Typical retraining time |
|---|---|---|
| SOC analyst (tier 1) | Security fundamentals certification, networking and operating-system basics, demonstrable log analysis, willingness to work shifts | 6-12 months from outside IT; 3-6 months from a support role |
| IT support or systems administrator (stepping stone) | Hardware, operating system and networking fundamentals, ticketing experience; often no certification at all | 2-5 months |
| GRC or security compliance analyst | Audit, policy or documentation background, familiarity with a control framework, strong writing | 4-9 months, shorter with an audit background |
| Identity and access management administrator | Directory services and cloud identity concepts, joiner-mover-leaver processes, basic scripting | 6-12 months |
| Vulnerability management analyst | Networking, asset inventory and patching knowledge, comfort with scanner output and prioritisation | 6-12 months |
Notes on the table:
- Penetration testing and incident response leadership are not entry points, whatever the advertising says. They are destinations you reach after two to five years in one of the roles above.
- Requirements vary sharply by employer. A large bank may insist on a degree and a specific certification; a 200-person company may hire the support technician who showed an interest. Government roles in the US frequently require citizenship and the ability to hold a clearance, and the process is run by the agency, not by you — ask the agency recruiter what applies. Outside the US, expect different frameworks and vetting rules entirely, so check with the relevant national cyber body or your country's professional association.
- Pay varies by role, sector, city and shift pattern, and shift differentials change the picture in 24/7 teams. Check the BLS Occupational Outlook Handbook entry for information security analysts, your state workforce agency, and live postings in states with pay-transparency rules, where ranges are published in the advert.
- Titles are inconsistent. The same work is advertised as security analyst, cyber defence analyst, SOC engineer and threat monitoring analyst. Read the duties, not the title.
The plan (timeline)
This assumes you are working full time and studying around it. Compress it if you are already in IT.
Months 0-3: decide, set up, start studying
- Choose one target role from the table above and write it at the top of a document you keep updated.
- Pull ten live job postings for that role in your area and list every tool, framework and certification named in them. That list is your syllabus.
- Register for a vendor-neutral fundamentals certification — CompTIA Security+ or the ISC2 Certified in Cybersecurity are the two most commonly named in entry postings — and book the exam date before you feel ready, so the deadline is real.
- Build a home lab on your own machine using free virtualisation software: a Linux virtual machine, a Windows virtual machine, and a network between them.
- Learn three tools properly rather than ten badly. Wireshark for traffic, Nmap for discovery, and the command line of both operating systems.
- Attend one local security meetup or professional association chapter meeting in person and talk to two people who hold the job you want.
- Tell your current IT or security team that you are studying, and ask the manager what internal security tasks you could take on.
Months 3-6: pass, build, document
- Sit the certification exam. If you fail, rebook within three weeks rather than losing momentum.
- Complete three lab projects and write each one up in a page: what you built, what you found, what you would do differently. A phishing email analysis, a log review that identifies a brute-force attempt, and a vulnerability scan with a prioritised remediation list cover most of what a tier-1 interview asks about.
- Put those write-ups somewhere public — a simple blog or a code repository — and link them from your CV.
- Rewrite your CV around the posting language you collected in month one, with a two-line summary that states the change explicitly.
- Request three informational conversations with SOC managers or security leads through your meetup contacts. Ask what they screen out on, not for a job.
- Volunteer for the security-adjacent work inside your current employer: access reviews, policy drafting, the annual security awareness rollout, audit evidence gathering.
Months 6-12: apply, interview, adjust
- Apply steadily rather than in bursts — a consistent handful of well-matched applications each week beats a hundred scattergun ones.
- Prioritise employers who hire internally into security: managed service providers, large IT departments and companies where you already work.
- Practise scenario questions aloud — "an alert fires for impossible travel on a user account, what do you do first?" — because tier-1 interviews are almost entirely scenarios.
- Ask every interviewer who rejects you what was missing, and fix the most common answer.
- Add a second, role-specific certification only if your target postings keep naming one you lack.
- Reassess at month nine. If nothing has moved, take a support or sysadmin role as a stepping stone instead of continuing to apply directly into security.
What goes wrong: people collect certifications instead of evidence, refuse the stepping-stone job because it feels like a step backwards, and apply only to the famous employers who receive thousands of applications. The changers who get through are usually the ones who took an unglamorous IT role and moved sideways eighteen months later.
The money side (list)
Plan the finances before you book an exam, not after you resign.
- Self-study route — the cheapest. One certification exam fee plus a study guide and a practice test bundle. Exam fees are set by the certification body and change, so check the current price on the certifying organisation's own site, and look for discount vouchers bundled with official study material. Budget for one retake; a meaningful share of first-time candidates fail.
- Community college certificate — middle of the range. Priced per credit hour, so the total depends on the number of credits and whether you qualify for in-district or in-state tuition. Out-of-state rates can be several times higher. Check the specific college's tuition page and ask the admissions office whether certification exam vouchers are included.
- Intensive bootcamp — the expensive end. Typically several thousand dollars upwards, and sometimes well into five figures for full-time programmes. The spread is driven by length, whether it is live or recorded, and whether career support is included. Ask for the completion and outcome figures in writing, ask what "placement" means in their definition, and talk to two graduates who are not on the provider's reference list.
- Degree — the longest and costliest. Only worth it if your target employers or a government agency genuinely require one, or if your employer funds it.
- Money you may not have to spend. Ask your employer's HR team about tuition reimbursement before paying for anything. Check whether your state workforce agency funds IT and cybersecurity training for career changers. If you served in the US military, ask a VA education counsellor what your benefits cover. Some certification bodies offer discounted or free fundamentals training to specific groups — check their site directly.
- The pay dip is real and depends where you come from. If you move from a senior role in another field to a tier-1 analyst post, expect a step down in the first job and a recovery over two to four years as you specialise. If you move from IT support into security, the move is more often sideways or upward. Shift work in a 24/7 team may add a differential. Check the BLS Occupational Outlook Handbook, your state workforce agency and published ranges in pay-transparency states for current numbers rather than relying on anything you read on a forum.
- Hold a savings buffer. Three to six months of essential expenses if you are studying while employed and only changing jobs at the end. Six to twelve months if you intend to quit to study full time, if you are the only earner, or if you are moving into a city where you have no network. Treat the buffer as untouchable and keep the training spend separate from it.
- Count the hidden costs. Exam retakes, annual certification maintenance fees and continuing education credits, a machine with enough memory to run two virtual machines, a cloud account for lab work, conference tickets, and the commuting or relocation cost if the roles near you are on-site.
- Set a stop point. Decide in advance what you will spend and how long you will give it — for example, [$X] and twelve months — and what you will do if the direct route has not worked by then. A stepping-stone IT role is a plan, not a failure.
Frequently asked questions
Am I too old to change into cybersecurity at 40 or 50?
Age is not a formal barrier, and security teams routinely hire people in their forties and fifties, particularly into governance, risk and compliance, audit-adjacent and project roles where judgement and sector knowledge matter more than speed. The practical issues are different from the ones people worry about. You may be interviewed by somebody younger and start below your current seniority. You may be competing with twenty-two-year-olds for a tier-1 monitoring seat where the employer assumes shift flexibility. And you have less time to absorb a pay dip before retirement, which makes the savings buffer and the choice of entry role more important than it would be at twenty-five. Aim at roles where your previous career is an asset rather than irrelevant — healthcare, finance, manufacturing or public sector experience makes you more useful to a security team in that same sector, not less.
Do I need a degree to work in cybersecurity?
It depends entirely on the employer and the country. Many US private-sector employers hire on certifications and demonstrated skill, and some have formally dropped degree requirements from their postings. Large regulated employers, defence contractors and many government agencies still list a degree, sometimes with a substitution clause allowing years of experience or a specified certification instead — read the substitution wording in the posting itself, because it is often more generous than the headline requirement. Outside the US, degree expectations and recognised credentials differ, so check with the national cyber body or professional association where you intend to work. If you do not have a degree, do not let it stop you applying; let the employer reject you rather than rejecting yourself.
How do I explain the career change on my CV and in interviews?
State it in the first two lines of your CV rather than hoping nobody notices, and frame it as continuity rather than escape. A workable structure for the interview answer is: what you did, the specific moment the security work started pulling you, what you have done about it since, and why this role in particular. For example: "I spent [number] years in [previous field], and the part I kept gravitating towards was [specific task — access reviews, incident reporting, data handling]. I took that seriously enough to pass [certification] and build [project], and I want the analyst role because [specific reason about this team]." Never criticise your old field, and never say you are looking for better pay or job security, even if that is part of it. Have one concrete story about something you found or fixed in your home lab ready to tell in under two minutes.
Can I get into security with no IT background at all?
Yes, but the route is usually longer and goes through an IT role first. Security work sits on top of networking, operating systems and identity, and a hiring manager who has to teach you all three plus the security layer will usually pick somebody else. Two honest options: spend six to twelve months getting the fundamentals and a support or service desk job, then move sideways into security from inside; or target the roles where your existing non-technical strengths dominate, which usually means governance, risk and compliance, security awareness or third-party risk. Both are legitimate entries. The route that rarely works is applying directly to analyst postings with a certification and no evidence of hands-on work.
How long does the change usually take?
From outside IT, plan for 9 to 18 months part-time to a first security or security-adjacent role, and longer if you need a stepping-stone job in between. From an IT support, networking or internal audit role, 3 to 6 months is realistic because most of the background is already there. What widens the spread is study hours per week, the strength of the local job market, whether you are willing to relocate or work shifts, and whether you have anyone inside the field who will talk to you about openings. Set a review point at nine months and change tactics if nothing has moved rather than repeating the same application.



