Who this page is for
This page is written for executives, IT and security leaders, compliance functions and curious newcomers. It serves as an entry hub and points to deeper topic pages.
What cyber security covers
Cyber security includes all measures that protect digital systems, data and identities from unauthorised access, manipulation and outage. It affects endpoints, networks, cloud services, applications, supply chains and people.
In practice cyber security blends technical controls with organisational process. Only the combination of people, process and technology delivers resilient security.
Key protection areas
Identity and access: accounts, MFA, privileged rights, SSO, zero trust approaches.
Endpoints: hardening, patching, EDR, encryption, secure onboarding.
Network: segmentation, firewalls, secure remote access, DNS protection.
Cloud: secure configuration, IAM, CSPM, secret management, logging.
Data: classification, encryption, backup, retention and deletion.
Applications: secure development, dependencies, testing, production hardening.
People: awareness, reporting culture, leadership training.
Processes: governance, risk management, incident response, vendor management.
Risk, resilience and compliance
Cyber security is rarely viewed in isolation today. It is part of risk and resilience management and closely tied to European regulatory frameworks such as NIS2, DORA and the Cyber Resilience Act.
The goal is not maximum security at any cost, but a reasonable reduction of risk relative to business value, threat and effort.
Detection and response
Assuming that attacks may succeed, protective controls are complemented by detection and response. SIEM, EDR and a rehearsed incident response process are the core building blocks. Reliable backups and clear incident communication matter just as much.
Common misconceptions
Cyber security is not finished once a tool is installed. It is not only the job of the IT team. And it does not work through panic or blame, but through calm, continuous work against a realistic risk picture.
A practical scenario
A mid-sized company with around 300 employees rolls out MFA and EDR, integrates its mail gateway properly, defines a simple incident response plan and rehearses it once a year. Three months later EDR blocks an attempted phishing login. Because escalation paths are clear, the incident is closed in two hours with no damage.
Where to go next
Deeper pages cover each building block. Good starting points are What is cyber security, Cybersecurity for business and Cybersecurity for SMEs. Regulated organisations may want to begin at NIS2 or DORA.
Checklist
- Document protection goals: confidentiality, integrity, availability
- Maintain a current asset and identity inventory
- MFA on all privileged and external access
- Patch and vulnerability management in place
- Backup strategy with tested restore
- Logging and detection focused on critical systems
- Incident response plan written and rehearsed at least yearly
- Awareness programme with a clear reporting culture
- Vendor and third-party risk reviewed in a structured way
Frequently asked questions
+What is the difference between cyber security and IT security?
IT security traditionally focuses on systems and networks. Cyber security extends the view to identities, cloud, supply chains and attacker behaviour.
+Do small companies need a SOC?
Not necessarily their own. Managed SOC or MDR models are often more economical than a full in-house 24/7 operation.
+Where to start?
With a clear asset inventory, MFA, backups, patch management and a rehearsed incident response plan. Everything else builds on top.
+How does compliance fit in?
Frameworks such as NIS2 or DORA set minimum requirements. Good security work usually meets them, but documentation and reporting paths must be prepared explicitly.
Related topics
Cyber security protects digital assets from attack, manipulation and outage. This page explains in plain language what it covers, how it differs from IT and information security and which measures are part of today's standard.
Effective enterprise security combines governance with concrete technical and organisational controls. This page shows what decision makers and IT leaders should focus on first - calm, practical and clearly prioritised.
SMEs do not need enterprise security architecture, but they do need the right basics. This page shows which measures deliver the most impact on a limited budget and which common mistakes are easy to avoid.
The NIS2 directive raises the cyber security bar in the EU noticeably. This page offers editorial orientation - not legal advice.
A security operations centre combines people, process and technology to detect cyber incidents early, handle them in a structured way and learn from them. This page covers tasks, models and common pitfalls.
A security incident requires a clear process, rehearsed roles and prepared communication. Improvising during an incident wastes time and creates mistakes. This page covers the phases, responsibilities and common pitfalls.
MFA significantly reduces the risk of compromised accounts. This page explains which methods actually work, where the weak points are and how to prioritise rollout in practice.
Identities are a primary target today. Clean handling of accounts, roles and permissions reduces the risk of many incidents significantly.
Zero trust is an architectural principle, not a product. It means: trust nothing automatically, verify every access based on identity, device and context.
Cloud security combines safe configuration, strong identities, good logging and clear responsibility. This page outlines the core building blocks.