Securitylab•October 6, 2026•🇷🇺Translated from Russian

Entering Cybersecurity Without a Specialized Degree: Sector Rules and Practical Entry Points

Many aspiring professionals wonder whether it makes sense to pursue a career in information security without a specialized higher-education diploma. The answer depends heavily on the target sector. In state security structures and regulated government organizations, formal education requirements are strict. In private companies, recruiters place far greater emphasis on practical understanding of networks and systems.

Security work can be divided into three broad segments. The first covers national security bodies, law enforcement, and classified information handling. The second includes state organizations that must comply with legislation and regulatory demands. The third segment consists of private businesses ranging from small firms to large enterprises.

In the first two segments, entry rules are formal. Candidates need a specialized higher-education degree in information security or programs officially coordinated with regulators. Those aiming for government roles should therefore evaluate these educational pathways carefully.

Private-sector hiring follows a different logic. Candidates must demonstrate concrete knowledge and hard skills, proving they understand the technologies they will protect. It is possible to enter without a specialized diploma, begin in a junior role, and advance from there.

What Private Companies Expect from Junior Engineers

Job postings for entry-level security engineers consistently list similar requirements: understanding of computer networks, knowledge of Windows Server and Linux, and basic familiarity with information-protection tools.

During interviews, recruiters test mechanical understanding. A typical question asks what happens when a user types google.com into a browser and how the request travels through each stage to the server. The ability to explain this process step by step reveals more about foundational knowledge than any line on a résumé.

This focus stems from the nature of the work itself. Corporate infrastructure comprises switches, routers, firewalls, servers, and endpoints. Protecting it requires knowing how these components interconnect and which traffic flows should never occur.

Real-World Career Paths Without a Relevant Degree

Experienced specialists who have spent around 15 years in hacking and now work at major companies include graduates of history faculties and former accountants. Their routes usually began with system administration, progressed through more complex tasks, and included Cisco networking certifications. Such stories are common in the industry.

Security work resembles creative problem-solving rather than template-based tasks. Success therefore depends on knowledge, skills, motivation, and growth potential. Hiring managers look for individuals who are genuinely engaged with the subject; the standard 9-to-6 mindset rarely leads to long-term success.

When a Diploma Exists but Foundations Are Missing

The opposite situation also occurs: a diploma is present yet practical understanding is absent. In Russian universities, hundreds of thousands of IT students are currently enrolled, yet many will graduate with knowledge that has already become partially outdated because technology evolves faster than curricula.

Large companies observe that only about one in twenty interns remain in the profession; the rest treat the role as a checkbox and disappear at the first difficulty. Candidates who claim to have solved 300 machines on HackTheBox are sometimes asked to explain one solution in detail and cannot, revealing that they followed published walkthroughs without comprehension.

Four Ways to Demonstrate Competence Without a Diploma

When no formal document exists, skills become the primary evidence. Four pillars are especially important:

  • Experience building personal infrastructure by deploying virtual machines, network equipment, and connectivity on a home computer.
  • Ability to troubleshoot by reading logs, searching documentation, testing hypotheses, and isolating root causes.
  • Vendor-independent understanding of technologies, allowing quick adaptation from Cisco to domestic switches or from classic Linux to Astra Linux, ALT Linux, or Red OS.
  • Tangible results presented through short lab reports that form a portfolio for technical interviews.

Many large companies also open internships to career changers and professionals over 40. Weekly participation in real tasks can lead to roles in penetration testing, presales, or general engineering with competitive compensation.

Self-Assessment Checklist Before Applying

Before submitting applications, candidates should verify they can explain browser-to-server communication, understand IP addresses and default gateways, work confidently in the Linux command line, describe Windows domain architecture, have deployed multi-VM labs, and grasp the functions of firewalls, intrusion detection systems, and SIEM.

Free introductory courses on attack and defense provide a useful reality check. Those who struggle with entry-level topics should strengthen fundamentals before pursuing specialization. The first year in the profession is typically demanding; meaningful comfort and enjoyment usually appear after three to five years.

Throughout October, CyberED offers open access to its “Engineer in Information Security” course, SOC and pentest programs, and workshops on AI agents and current threats after simple registration.

Related articles

Habr•Policy & Regulation

Roskomnadzor Deploys 2.27 Billion Ruble AI Traffic Filter: Known Facts and Expert Speculations

Russian regulator Roskomnadzor has integrated a machine learning-based traffic filtering system into the automated security infrastructure of the Russian internet segment. The system, valued at 2.27 billion rubles, operates on domestic models within the agency's own infrastructure and connects to TSPU equipment that performs DPI-based filtering. Publications including Forbes, Meduza, 3DNews and SecurityLab base their reporting on the 2026 digital transformation passport, which also allocates additional billions for TSPU upgrades and hardware. Experts suggest the model analyzes packet sizes, session durations, traffic ratios and server characteristics rather than relying solely on known signatures, though no official performance metrics have been released. The exact role of the model—real-time analysis versus signature generation—remains unconfirmed, as does its impact on VPN protocols and potential for false positives affecting corporate and cloud traffic.

Habr•Policy & Regulation

MinTsifry Proposes Requiring Telecom Operators to Install SORM Equipment Before Obtaining Licenses

The Russian Ministry of Digital Development plans to introduce legislation obligating telecom operators to deploy SORM surveillance systems prior to receiving operating licenses. Under the proposed rules, companies will only be permitted to begin serving subscribers after the equipment has been installed and handed over to law enforcement agencies. Non-compliance could result in license revocation through an extrajudicial administrative process. Current regulations allow operators to obtain licenses with a network diagram that merely indicates planned or existing SORM components. The change aims to close loopholes exploited by unscrupulous providers that repeatedly register new legal entities to operate without surveillance capabilities. Industry experts note that the minimum cost of a basic SORM complex starts at 5 million rubles, which could disproportionately affect smaller local providers without a transition period or scaled requirements.

Habr•Policy & Regulation

GOST R 57580 Compliance: Defining Assessment Scope to Verify Real Protection in Financial Organizations

Financial institutions often maintain extensive documentation on information security yet still fail GOST R 57580 assessments due to mismatches between documented processes and actual infrastructure. The standards GOST R 57580.1-2017 and GOST R 57580.2-2018 set distinct requirements for protection levels and evaluation methodology. Correct application begins with identifying the organization's regulatory category under Bank of Russia rules such as Regulation 851-P for credit institutions or Regulation 757-P for non-credit financial organizations. Defining the precise assessment boundary is critical, including systems, remote access channels, virtualization components, and third-party interactions. Organizations must also distinguish between the full assessment scope and the representative sample selected for verification. Evidence collection requires both policy review and technical confirmation that controls function as intended across the evaluated environment.

Habr•Policy & Regulation

Evaluating Secure Development Maturity: Comparing BSIMM, DSOMM, SAMM and GOST R 56939-2024

A detailed analysis compares four methodologies for self-assessing secure software development maturity in Russian companies. The review covers BSIMM from Black Duck, OWASP DSOMM, OWASP SAMM and the updated Russian national standard GOST R 56939-2024. Each model was tested through a simulated audit on a fictional company called ООО «Лиса и лосЬ» that uses GitLab, Nexus and SonarQube. The evaluation scored the methodologies on criteria including ease of maturity calculation, recommendation generation, roadmap building, heat-map creation and SDLC coverage. GOST R 56939-2024 and SAMM received the highest total scores of 35 and 34 out of 47. The article concludes that no single methodology covers all needs and recommends combining approaches tailored to specific company contexts.