Home/Explore topics/Training & research

Training & research

Training & research

Cybersecurity learning develops verifiable skills in networks, systems, application security, investigation and governance. This topic connects primary documentation, authorised labs and critical reading of research. It helps choose a path based on starting skills and produce learning evidence rather than a list of tools or certificates.

LearningResearchOpen source
Empty intelligence archive with dossiers and maps
AI-generated editorial illustration

How should you read cybersecurity research? Identify the question, data, method and baseline. A laboratory result depends on the chosen hardware, test set and assumptions. It does not automatically measure risk or effectiveness in your environment.

For a benchmark, examine example provenance, separation of training and evaluation, error definitions and excluded cases. For application testing, ask for authorised scope, reproduction conditions and observations. A useful conclusion describes both what works and situations where the experiment cannot support a conclusion.

In this topic

Training · Labs · Publications · Exercises · Careers · Communities

Practical guides

Build a cybersecurity learning path

How can cybersecurity progress be measured? Choose a task you must explain and carry out in an authorised lab. Define prerequisites, documentation, exercises and the expected outcome. Learning evidence can be an annotated configuration, log analysis or reproducible report. Distinguish observed results, assumptions and lab limitations before applying an exercise to a real environment.

Read the guide

Intelligence watch

Open the news desk →

Saved headlines · source refresh unavailable · Last successful fetch : Oct 22, 2026, 9:25 PM

References: data, uses and limitations

Documentation reviewed on .

References: data, uses and limitations
Source and purposeVerified data or benchmarkHow to use itLimitation to retain
MITRE · Common Weakness Enumeration

Name classes of software and hardware weakness.

 A CWE describes a weakness that can contribute to vulnerabilities. It does not represent a particular incident. Connect the weakness to the observed mechanism: input, processing and missing control. Use it to fix the cause and plan regression tests.

Explore the method →

 A keyword in a report alone does not establish the correct CWE classification.
W3C · WCAG 2.2

Evaluate accessibility criteria for web content.

 WCAG 2.2 is a W3C Recommendation. Success criteria have A, AA and AAA levels. Define tasks, pages and states, then combine inspection, keyboard, zoom and relevant assistive technology. Keep reproduction steps for barriers.

Explore the method →

 An automated scanner does not establish conformity of a complete journey. Evaluation must cover interactive states and actual content.
Google · Core Web Vitals

Distinguish loading, responsiveness and visual stability.

 Good thresholds are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1 at the 75th percentile, segmented by mobile and desktop. Separate field measurement from laboratory tests. Record period, URL, device, population and sample size before comparing changes.

Explore the method →

 These thresholds are not measured results for this site. A good lab score alone does not establish visitor experience.