In dit dossier
Training · Labs · Publications · Exercises · Careers · Communities
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.
Lees de gids ENNieuwsoverzicht
Alle internationale nieuwsberichten →Opgeslagen koppen · vernieuwen niet beschikbaar · Laatst succesvol opgehaald : 22 okt 2026 21:24
Google brengt Harness2 uit, AI-agenten die zichzelf verbeteren - Pasquale Pillitteri
via Google News · aggregatorAnthropic zegt dat Claude 26% van haar AI-onderzoek en -ontwikkeling leidt - Unite.AI
via Google News · aggregatorWorkday technisch onderzoeksteam levert betrouwbare en efficiënte AI - Dutch IT Channel
via Google News · aggregatorSSI and NVIDIA partner to accelerate AI research with Vera Rubin ... - eeNews Europe
via Google News · aggregatorTU/e verleent eredoctoraat aan Christian Borgs - Eindhoven University of Technology
via Google News · aggregatorHow Balyasny Asset Management built an AI research engine - OpenAI
via Google News · aggregatorReferenties: gegevens, gebruik en grenzen
Documentatie geraadpleegd op .
De uitgebreide toelichtingen zijn in deze editie beschikbaar in het Engels.
| Bron en doel | Gecontroleerde gegevens of maatstaf | Praktisch gebruik | Te behouden beperking |
|---|---|---|---|
| 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. | 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. | 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. | These thresholds are not measured results for this site. A good lab score alone does not establish visitor experience. |

