Logo
Cybersecurity

Cybersecurity Skills Need Maintenance Too

Cyber professionals don’t finish learning when the course ends. The systems they protect certainly don’t stop changing.

ITSEC AsiaITSEC Asia
|
Sep 14, 2026
Cybersecurity Skills Need Maintenance Too

A cybersecurity professional completes training on Friday. They’ve worked through the material, passed the assessment and returned to their job with a fresh set of skills.

Six months later, the environment looks different.

A cloud service has changed. The team has introduced AI tools. Attack techniques have evolved. Someone redesigned the incident process. Three new systems appeared and one old application that was supposedly retiring is, mysteriously, still alive.

This is why cybersecurity training increasingly needs to behave less like an annual event and more like professional maintenance.

NIST’s FISSEA Fall Forum on 15 September puts that idea into practice. Its agenda includes an interactive session on building a micro training module, followed by examples of cybersecurity learning tied to the NICE Workforce Framework and practical skill application.

The format matters. Learning doesn’t always need another full week away from work.

Small Learning Can Solve Specific Problems

CISA already uses micro learning as part of its cybersecurity training model. Its Continuous Diagnostics and Mitigation program offers short modules of roughly 3 to 10 minutes, designed to build foundational knowledge before deeper demonstrations and hands on activities.

That combination makes sense for cybersecurity.

A short module could refresh one narrow concept before a team practises it:

  • How to interpret a particular security signal
  • What changed in an incident escalation procedure
  • How a new cloud configuration affects access
  • What evidence should be preserved during an investigation
  • How a recent attack technique changes an existing playbook

The goal isn’t to compress an entire cybersecurity discipline into eight cheerful minutes. Some subjects deserve hours, days or considerably longer.

Micro learning works when the learning objective is equally focused.

Skills Have to Stay Close to the Work

Continuous learning becomes more useful when it connects directly to what people actually do.

A SOC analyst could review a new detection technique and immediately test it against a simulated incident. A penetration tester could study one unfamiliar vulnerability class before working through a vulnerable application. A cloud security practitioner could learn a configuration change and then diagnose a deliberately misconfigured environment.

ENISA takes a similar practical view of cybersecurity skills development. Its training and exercise approach centres on testing capabilities, identifying gaps and improving technical and operational competence.

That cycle matters: learn, apply, discover the gap, improve and repeat.

It also changes how organizations should think about training budgets. Sending someone to a substantial course can build capability. Keeping that capability current requires smaller opportunities to practise throughout the year.

Build a Learning Rhythm

A useful cybersecurity development plan might combine deeper structured training with shorter exercises, scenario refreshers and regular practical challenges.

The exact rhythm will vary by role. SOC teams may need frequent incident exercises. Penetration testers need exposure to new techniques and technologies. Managers need recurring practice making decisions during unfamiliar scenarios.

At ITSEC Cyber & AI Academy, hands on environments can support that progression by giving learners opportunities to practise cybersecurity skills against scenarios rather than leaving knowledge parked in course notes.

A certificate can mark the day someone completed training.

It can’t guarantee what they’ll still be able to do next March.

Explore practical cybersecurity and AI training at ITSEC Cyber & AI Academy.

References: NIST FISSEA Fall Forum, 15 September 2026 · CISA CDM Micro Learn Training · ENISA Trainings and Exercises

Share this post

You may also like

Cybersecurity Job Titles Don't Tell the Whole Story
Cybersecurity

Cybersecurity Job Titles Don't Tell the Whole Story

Two candidates apply for the same security analyst position. Both have relevant qualifications and list incident response among their skills. One can investigate an alert, correlate logs and explain when an incident needs escalation. The other understands the theory but has limited practical experience. On paper, they may look similar. At work, they will need different levels of supervision. This is a challenge for cybersecurity workforce planning. Job titles and qualifications help describe a candidate's background, but employers also need a reliable way to assess practical capability and identify what someone must learn before taking on greater responsibility. ENISA's European Cybersecurity Skills Framework provides a useful reference. Its 12 cybersecurity role profiles describe the responsibilities, skills, knowledge and competencies associated with different professional roles. ENISA is currently revising the framework to reflect developments such as AI and secure digital product lifecycles, with new proficiency levels planned to support clearer skills definitions, career pathways and workforce assessment. These issues will be discussed at its conference on 4–5 November 2026. ENISA [https://www.enisa.europa.eu/events/european-cybersecurity-skills-conference-2026?utm_source=chatgpt.com] The principle applies

ITSEC AsiaITSEC Asia
|
Okt 26, 2026 — 4 minutes read
The Reason Businesses That Skip Digital Forensics Keep Getting Hit Twice
Cybersecurity

The Reason Businesses That Skip Digital Forensics Keep Getting Hit Twice

INTRODUCTION The cybersecurity conversation has long been dominated by prevention. Organizations invest in perimeter defenses, deploy intrusion detection systems, and train employees to recognize phishing attempts. Yet according to IBM's Cost of a Data Breach Report 2024, the average time to identify a breach reached 194 days, nearly half a year of undetected attacker activity inside a network. This statistic reveals a painful truth: prevention alone is not a complete strategy. When an attacker does get through (and modern threat actors have made it a matter of when, not if), organizations need a structured, methodical way to understand exactly what happened, how far the damage extends, and what must change to prevent history from repeating itself. That capability is digital forensics. And the businesses that overlook it are not just leaving questions unanswered. They are setting themselves up to be compromised again. Source: IBM Cost of a Data Breach Report 2024 [https://newsroom.ibm.com/2024-07-30-ibm-report-escalating-data-breach-disruption-pushes-costs-to-new-highs], Ponemon Institute [https://www.ponemon.org] WHAT IS DIGITAL FORENSICS AND WHY DOES IT MATTER? Digital forensics is the process of collecting, preserving, analyzing,

|
Mei 06, 2026 — 7 minutes read
One Compromised System Rarely Stays One Compromised System
Cybersecurity

One Compromised System Rarely Stays One Compromised System

A business application stops working. The server itself is fine. The network looks normal. Authentication is available. Then someone discovers that an external service used by the application is unavailable. Suddenly the incident diagram gets bigger. ENISA’s Threat Landscape 2026, published on 22 September and discussed in a dedicated webinar on 29 September, puts this problem near the centre of its analysis. ENISA says the growing interconnectedness of digital ecosystems is increasing exposure to cyber risk and continues to observe attacks targeting dependencies, including supply chain and third party relationships. ENISA [https://www.enisa.europa.eu/publications/enisa-threat-landscape-2026?utm_source=chatgpt.com] For workforce development, there’s a practical lesson here: cybersecurity professionals need to understand dependencies as well as assets. AN ASSET LIST DOESN’T SHOW THE WHOLE RISK Knowing what systems an organization owns is useful. Knowing what those systems rely on is different. A customer portal might depend on an identity provider, DNS, cloud infrastructure, payment service, API, software library and managed service. Several other applications may rely on exactly the same components. Compromise one shared dependency and the blast radius changes quickly. Security

ITSEC AsiaITSEC Asia
|
Sep 30, 2026 — 3 minutes read

Receive weekly
updates on new posts

Subscribe