Open to every curious mind

Understand how systems fail. Then build ones that hold.

Cyber Denders is a place to grow real security knowledge: the principles that never change, the domains you can work in and the paths that lead to a career. No experience needed.

9core principles explained
24domains you can work in
4career tracks mapped

Break a cipher in your browser

The Caesar cipher is over 2,000 years old. Type a message, slide the shift, then see how fast it falls.

3

See why it fails: try all 26 shifts

    With only 26 possible keys, an attacker just tries them all. Modern encryption exists because of lessons like this one.

    How long would a password last?

    Type an example, not a real password. Nothing leaves your browser.

    0characters
    0bits of entropy, at most
    -to crack offline, at most

    The estimate assumes random characters and an attacker making 10 billion guesses per second. Words, names, dates and keyboard patterns fall much faster, which is why a password manager generating random passwords wins.

    One character changes everything

    A hash is a fingerprint of data. Edit the text and compare the two SHA-256 fingerprints.

    SHA-256 of your text

    SHA-256 of the same text with one extra dot

    A tiny change flips about half of the 256 bits. That is why hashes prove integrity: if a file's hash matches, the file has not been altered.

    Principles

    The principles everything else is built on

    Tools change every year. These ideas have guided security for decades, and every control you will ever configure traces back to one of them.

    The CIA triadwhat security protects

    Confidentiality

    Only authorized people and systems can read the data.

    What threatens it

    • Data leaks and misconfigured storage
    • Eavesdropping on unencrypted traffic
    • Stolen or guessed credentials

    What protects it

    • Encryption at rest and in transit
    • Access control and least privilege
    • Multi-factor authentication
    • Data classification

    Integrity

    Data and systems stay accurate, and change only in authorized ways.

    What threatens it

    • Tampering with files, logs or transactions
    • Malware that alters system behavior
    • Man-in-the-middle modification

    What protects it

    • Hashes and digital signatures
    • Change control and code review
    • File integrity monitoring
    • Backups you can compare against

    Availability

    Systems and data are there when legitimate users need them.

    What threatens it

    • Ransomware and destructive attacks
    • Denial-of-service floods
    • Hardware failure and human error

    What protects it

    • Tested backups and restore drills
    • Redundancy and failover
    • DDoS protection and capacity planning
    • Timely patching
    AuthenticationProving who you are.
    AuthorizationDeciding what you may do.
    AccountingRecording what you did.
    Non-repudiationYou cannot deny having done it.

    Defense in depth

    Layer independent controls so that one failure is not a breach.

    In practice MFA, a patched VPN, network segmentation, EDR and offline backups each cover for the others.

    Least privilege

    Give every user, service and process only the access it needs, for only as long as it needs it.

    In practice Admins use a separate admin account. Services run as non-root with scoped permissions.

    Zero trust

    Never trust a request because of where it comes from. Verify every one explicitly.

    In practice Check identity, device health and context on each access, even from inside the office network.

    Secure by default

    The safe configuration is the one you get without doing anything.

    In practice Firewalls deny by default. New accounts start with no permissions. Debug modes ship turned off.

    Fail securely

    When something breaks, it should fail closed, not open.

    In practice If the authentication service is unreachable, access is denied instead of waved through.

    Separation of duties

    No single person or account can complete a critical action alone.

    In practice One person requests a payment or a production change, a different person approves it.

    Keep it simple

    Complexity hides bugs. Small, understandable systems are easier to secure.

    In practice Remove unused services, plugins, open ports and old accounts. Less surface, fewer surprises.

    Assume breach

    Design and monitor as if an attacker is already inside.

    In practice Centralize logs, test your backups and rehearse an incident response plan before you need it.

    Open design

    Security should depend on keeping keys secret, never on keeping the design secret.

    In practice Use public, reviewed standards such as AES and TLS. Never invent your own cryptography.

    Domains

    Cybersecurity is not one job. It is 24 of them.

    Some people defend, some attack with permission, some build and some govern. Pick a group to see the work, the roles and who tends to enjoy it.

    Blue team

    Detect attacks, respond to them and keep the organization running.

    Security Operations (SOC)

    Monitor alerts around the clock, triage what is real and escalate what matters.

    Typical roles
    SOC analyst (L1 to L3)
    Good fit if you like
    spotting patterns and getting fast feedback

    Incident Response and Digital Forensics

    Investigate breaches, contain the attacker and reconstruct what happened from evidence.

    Typical roles
    Incident responder, forensic analyst
    Good fit if you like
    solving puzzles under pressure

    Threat Hunting and Detection Engineering

    Search for attackers that alerts missed, then write the detections that catch them next time.

    Typical roles
    Threat hunter, detection engineer
    Good fit if you like
    forming hypotheses and testing them in data

    Threat Intelligence

    Study adversaries, their tooling and their targets, and turn that into decisions defenders can act on.

    Typical roles
    CTI analyst
    Good fit if you like
    research, writing and connecting dots

    Vulnerability Management

    Find weaknesses, rank them by real risk and drive the fixes before attackers arrive.

    Typical roles
    Vulnerability analyst
    Good fit if you like
    prioritizing and getting things done across teams
    Red team

    Think and act like an adversary, with permission, to find weaknesses first.

    Penetration Testing

    Authorized, time-boxed attacks on applications, networks and cloud, ending in a report with fixes.

    Typical roles
    Penetration tester
    Good fit if you like
    breaking things methodically and explaining how

    Red Teaming

    Goal-driven adversary simulation that tests people, process and detection, not only technology.

    Typical roles
    Red team operator
    Good fit if you like
    stealth, patience and creative problem solving

    Vulnerability Research

    Discover previously unknown flaws in software and hardware, and report them responsibly.

    Typical roles
    Security researcher, exploit developer
    Good fit if you like
    deep technical work and long investigations

    Bug Bounty

    Independent testing on programs that invite it and reward valid reports.

    Typical roles
    Independent researcher
    Good fit if you like
    self-direction and persistence
    Security engineering

    Design and run the systems that make attacks hard in the first place.

    Security Architecture and Engineering

    Design secure systems and build the tooling that protects them.

    Typical roles
    Security engineer, security architect
    Good fit if you like
    systems thinking and building things that last

    Application Security and DevSecOps

    Threat modeling, code review and security checks built into the delivery pipeline.

    Typical roles
    AppSec engineer, DevSecOps engineer
    Good fit if you like
    writing code and working with developers

    Cloud Security

    Secure identity, configuration and workloads on AWS, Azure and Google Cloud.

    Typical roles
    Cloud security engineer
    Good fit if you like
    automation and infrastructure as code

    Identity and Access Management

    Decide who can access what: single sign-on, MFA, privileged access.

    Typical roles
    IAM engineer
    Good fit if you like
    precision and process design

    Network Security

    Firewalls, segmentation, VPN, intrusion detection and zero-trust network access.

    Typical roles
    Network security engineer
    Good fit if you like
    protocols, packets and troubleshooting

    Cryptography and PKI

    Keys, certificates and protocols that keep data private and authentic.

    Typical roles
    Cryptography engineer, PKI administrator
    Good fit if you like
    math-minded, detail-first work
    Risk and compliance

    Set the rules, measure risk and prove that controls work.

    Governance, Risk and Compliance

    Policies, risk assessments and frameworks such as ISO 27001 and NIS2.

    Typical roles
    GRC analyst, risk manager
    Good fit if you like
    structure, writing and seeing the whole organization

    Security Audit and Assurance

    Independently verify that security controls exist and actually work.

    Typical roles
    IT auditor
    Good fit if you like
    evidence, skepticism and clear reporting

    Privacy and Data Protection

    GDPR, impact assessments and responsible handling of personal data.

    Typical roles
    Data protection officer, privacy analyst
    Good fit if you like
    law meeting technology

    Security Awareness

    The human side: training, phishing simulations and a culture that reports mistakes.

    Typical roles
    Awareness lead
    Good fit if you like
    teaching and communication

    Security Leadership

    Strategy, budget and accountability for the security program.

    Typical roles
    Security manager, CISO
    Good fit if you like
    leading people and translating risk for executives
    Niche fields

    Deep expertise in one technology, platform or type of threat.

    Malware Analysis and Reverse Engineering

    Take malicious code apart to learn what it does and how to detect it.

    Typical roles
    Malware analyst, reverse engineer
    Good fit if you like
    assembly, debuggers and patience

    OT and ICS Security

    Protect industrial control systems in energy, water and manufacturing, where safety comes first.

    Typical roles
    OT security engineer
    Good fit if you like
    physical processes and engineering discipline

    Mobile, IoT and Embedded Security

    Test and harden phones, connected devices and firmware.

    Typical roles
    Mobile or embedded security engineer
    Good fit if you like
    hardware, radios and low-level code

    AI Security

    Secure machine-learning systems against threats such as prompt injection and data poisoning.

    Typical roles
    AI security engineer
    Good fit if you like
    a new field where the rules are still being written
    Careers

    There is more than one way in

    Very few people start in security. Most arrive from somewhere else and bring that experience with them.

    Where people come from, and where they land first

    • IT support or system administrationSOC, incident response, security engineering

      You already know how systems really run, and where they break.

    • Software developmentApplication security, DevSecOps, security tooling

      You can read code, which is where most vulnerabilities live.

    • NetworkingNetwork security, SOC, detection engineering

      You understand traffic, so anomalies stand out.

    • University (computer science or similar)Graduate and trainee roles, research

      Add internships and CTF competitions to turn theory into proof.

    • Self-taught through labs and CTFsJunior penetration tester, SOC analyst, bug bounty

      Publish write-ups and projects so employers can see your skill.

    • Law, audit or financeGRC, privacy, security audit

      You bring the regulatory and risk thinking that technical teams often lack.

    How a career grows, track by track

    1. Entry0 to 2 years

      SOC analyst L1, junior security analyst

      Triage alerts, follow playbooks and escalate what looks real.

      Skills to build
      Networking, Windows and Linux basics, reading logs, SIEM queries.
      Certifications often seen
      Security+, CySA+, BTL1, SC-200
    2. Mid2 to 5 years

      SOC analyst L2, incident responder, forensic analyst

      Lead investigations, run forensics and coordinate containment.

      Skills to build
      Memory and disk forensics, PowerShell or Python scripting, MITRE ATT&CK.
      Certifications often seen
      GCIH, GCFE, GCFA
    3. Senior5+ years

      Threat hunter, detection engineer, senior responder

      Hunt for what tools miss and turn findings into durable detections.

      Skills to build
      Detection as code, malware triage, threat intelligence.
      Certifications often seen
      GCFA, GNFA, GREM
    4. LeadLeadership

      SOC manager, incident response lead

      Run the team, the on-call process and the crisis when it comes.

      Skills to build
      People leadership, crisis communication, budgeting.
      Certifications often seen
      CISSP, CISM
    1. Entry0 to 2 years

      Junior penetration tester, security tester

      Test web applications and networks under supervision and write up findings.

      Skills to build
      OWASP Top 10, networking, Linux, an intercepting proxy, basic scripting.
      Certifications often seen
      eJPT, Security+, PNPT
    2. Mid2 to 5 years

      Penetration tester

      Lead engagements from scoping to the final report.

      Skills to build
      Active Directory attacks, cloud testing, clear report writing.
      Certifications often seen
      OSCP, BSCP, CRTP
    3. Senior5+ years

      Senior penetration tester, red team operator

      Simulate real adversaries, evade detection and build custom tooling.

      Skills to build
      Evasion techniques, tool development, social engineering.
      Certifications often seen
      OSEP, CRTO
    4. LeadLeadership

      Red team lead, principal researcher

      Design campaigns, mentor operators and present results to executives.

      Skills to build
      Program design, risk communication, research direction.
      Certifications often seen
      Experience counts most here
    1. Entry0 to 2 years

      Sysadmin, developer or network engineer with a security focus

      Harden systems, automate patching and fix what assessments find.

      Skills to build
      System hardening, scripting, infrastructure as code, one cloud platform in depth.
      Certifications often seen
      Security+, a cloud associate certification
    2. Mid2 to 5 years

      Security engineer, cloud security engineer, AppSec engineer

      Build security into platforms and pipelines so teams get it by default.

      Skills to build
      Threat modeling, CI/CD security, IAM, containers and Kubernetes.
      Certifications often seen
      AZ-500, AWS Security Specialty, CKS
    3. Senior5+ years

      Senior security engineer, security architect

      Set the design patterns other teams build on.

      Skills to build
      Architecture, zero-trust design, applied cryptography.
      Certifications often seen
      CISSP, CCSP
    4. LeadLeadership

      Principal architect, head of security engineering

      Own the technical security strategy and the team that delivers it.

      Skills to build
      Technical strategy, mentoring, vendor and budget decisions.
      Certifications often seen
      Experience counts most here
    1. Entry0 to 2 years

      GRC analyst, compliance analyst, junior auditor

      Maintain policies, collect evidence and support risk assessments.

      Skills to build
      ISO 27001, NIS2 and GDPR basics, risk assessment, clear writing.
      Certifications often seen
      ISO 27001 Foundation, Security+
    2. Mid2 to 5 years

      Risk manager, IT auditor, privacy specialist

      Run assessments and audits, and advise teams on closing gaps.

      Skills to build
      Audit technique, control frameworks, stakeholder management.
      Certifications often seen
      CISA, ISO 27001 Lead Implementer or Lead Auditor, CIPP/E
    3. Senior5+ years

      Senior GRC consultant, security manager, DPO

      Own the risk register and the conversation with regulators.

      Skills to build
      Risk quantification, regulatory strategy, program management.
      Certifications often seen
      CISM, CRISC, CISSP
    4. LeadLeadership

      CISO, head of risk

      Accountable for the whole security program and its reporting to the board.

      Skills to build
      Executive communication, governance, budgeting.
      Certifications often seen
      Experience counts most here

    About certifications. They help you pass the first filter, but projects and hands-on skill get you through the interview. Timelines vary widely, and some certifications have prerequisites: CISSP, for example, requires five years of professional experience (four with a relevant degree).

    Make yourself hireable

    • Build a home lab. A few virtual machines, one of them deliberately vulnerable, teach more than any course.
    • Publish what you learn. Write-ups, scripts and small tools are proof an employer can check.
    • Learn to write. Every security job ends in a report, a ticket or an explanation to someone non-technical.
    • Pick one track and go deep. Breadth comes later. Depth gets you the first job.
    • Compete. CTFs build skill under pressure. In Romania, look at UNbreakable România and the Romanian Cyber Security Challenge.
    • Meet the community. Local meetups, OWASP chapters and conferences such as DefCamp in Bucharest are where jobs and mentors appear.
    Foundations

    The skills every track shares

    Whichever domain you choose, the first steps are the same. Follow the line from the top, or jump in where you already have footing.

    1. How things connect

      You can't defend what you don't understand. Learn how computers, networks and the web talk to each other.

      • TCP/IP
      • DNS
      • HTTP and TLS
      • Linux command line
      Start here
    2. Defending a server

      Take a fresh Linux machine and make it hard to break: key-based SSH, a firewall, automatic updates, least privilege and readable logs.

      • SSH hardening
      • Firewalls
      • Patching
      • Logging
      Next
    3. Web application security

      Learn why injection, broken authentication and misconfiguration keep topping the charts, and how to prevent them.

      • OWASP Top 10
      • Authentication
      • Input validation
      • Secure headers
      Then
    4. Detection and response

      When something goes wrong, calm method beats panic. Collect evidence, build a timeline, find the entry point, recover cleanly.

      • Log analysis
      • Triage
      • Digital forensics
      • Incident playbooks
      Later
    5. Thinking like an attacker, legally

      Capture-the-flag games and responsible disclosure teach you to see weaknesses first. Scope and permission come before every technique.

      • CTF competitions
      • Threat modeling
      • Responsible disclosure
      When you're ready
    Security checkup

    The 5-minute security checkup

    Six habits that block the majority of everyday attacks. Tick them off as you go.

    0/6habits in place
    Solid baseline. Keep learning.
    Practice safely

    Where to practice, legally

    These platforms are built for learning. Everything on them is legal to attack, so go break things.

    Reference

    OWASP

    The standard references for web risks, plus Juice Shop, a vulnerable app to practice on.

    CTF

    picoCTF

    Beginner-friendly capture-the-flag challenges that teach as you play.

    Guided

    TryHackMe

    Guided rooms that take you from zero to confident, step by step.

    Advanced

    Hack The Box

    Realistic machines and challenges when you want a tougher test.

    Reference

    MITRE ATT&CK

    A map of real attacker techniques, ideal for learning to defend.

    The golden rule: only test systems you own or have explicit written permission to test. Unauthorized access is a crime, in Romania and almost everywhere else.

    For system administrators

    Incident Response Methodology

    A step-by-step field guide for the day something goes wrong: what to do in the first 15 minutes, triage commands for Windows and Linux, containment, recovery and the reporting deadlines that apply in Romania. Available in English and Romanian.

    Open the methodology
    1. Preparation
    2. Detection and analysis
    3. Containment
    4. Eradication and recovery
    5. Lessons learned

    Got a question, or something to teach?

    Suggest a topic, share a resource or just say hello. We read every message.

    Write to us