Skip to content
Sign in
Artwork for Ethical Hacker & Cyber Defence
EducationCourses

Ethical Hacker & Cyber Defence

Ilaria Digital School

Become a cybersecurity specialist, from scratch to professional penetration testing: understand systems and networks, attack ethically within an authorised scope, defend, investigate and secure development. Skills: Master the mathematical foundations of computing and cryptography; Understand computer and operating system architecture, administer Linux; Design and analyse a network; Program in Python and optimise algorithms; Secure an information system; Design and query a database; Use artificial intelligence in attack and defence; Test the security of web and mobile applications; Carry out a complete penetration test and its report; Conduct a digital forensic investigation; Analyse malware; Develop securely; Integrate security into continuous integration and deployment; Analyse risks and audit an organisation's security. Workshops take place in your isolated lab, on training targets and samples you install yourself; no real system is touched, and the data you need is provided.

Play
Open in
  • 214 episodes
  • Avg 15 min
  • English

Episodes 214

NewestOldestLongest
All20Unplayed20In progress0Played0
Counted on this page — what you have heard stays on this device, so it is not something the list can be paged by.
  • September 22 · 15 min

    Develop a test checklist based on the threat model

    THEORETICAL RECAP A threat model is a structured description of what can go wrong in an application: assets to protect, entry points (attack surface), threats (typically classified via STRIDE: Spoofing, Tampering, Repudiation, Information disclosure,...

  • September 22 · 15 min

    From modeling to test plans — a practical and practical bridge

    So far, you have learned to identify an attack surface, to apply security principles, to model threats with STRIDE, and to prioritize risks using the OWASP Risk Rating Methodology. All of this is analytical work. But analysis alone changes nothing ab...

  • September 21 · 15 min

    Visual summary — Mental map of the concepts seen

    This chapter closes the section on Application Security Principles and Threat Modeling. Its purpose is not to introduce new material, but to assemble everything you have studied into a single coherent mental map. A mental map is a way of representing...

  • September 21 · 15 min

    Varying the scoring on an e-commerce API

    THEORETICAL RECAP Risk scoring turns a vague sense of danger into a comparable number so you can prioritize corrections and tests. The OWASP Risk Rating Methodology models Risk = Likelihood x Impact. Likelihood is estimated from Threat Agent factors ...

  • September 18 · 15 min

    Heuristics to prioritize corrections and tests

    In the previous activities, you learned to identify the attack surface of an application, to map threats using the STRIDE model, to apply secure design principles, and to score threats with the OWASP Risk Rating Methodology (probability versus impact...

  • September 18 · 15 min

    Score previous threats with OWASP Risk Rating

    THEORETICAL RECAP The OWASP Risk Rating Methodology estimates the severity of a threat by combining two dimensions: Likelihood (how probable an attack is) and Impact (the damage it causes). Each dimension is broken into factors scored from 0 to 9. Li...

  • September 17 · 15 min

    OWASP Risk Rating Methodology — probability vs impact

    In the previous activities, you built a threat matrix for the Blog, mapped its attack surface, and applied secure design principles such as Least Privilege and Defense in Depth. You also practiced classifying threats with STRIDE. Now that you can ide...

  • September 16 · 15 min

    Map the Blog's attack surface

    THEORETICAL RECAP The attack surface is the sum of all points where an unauthorized actor can attempt to enter, extract, or manipulate data within a system. It includes entry points (HTTP endpoints, forms, APIs, file uploads, cookies, headers), data ...

  • September 15 · 15 min

    Attack surface — definition and identification

    The attack surface is one of the most important concepts in application security and threat modeling. Now that you have practiced drawing Data Flow Diagrams, applying the STRIDE methodology, building threat matrices, and evaluating applications again...

  • September 15 · 15 min

    Adapting the principles to a file upload microservice

    THEORETICAL RECAP Secure design principles are not abstract rules; they are decision filters you apply to concrete features. Least Privilege means every component (service account, container, database user, storage bucket) holds only the permissions ...

  • September 14 · 15 min

    Case study — Incident due to the absence of Least Privilege

    In the previous activities, you learned to model threats with STRIDE, to draw Data Flow Diagrams, to build a threat matrix, and to evaluate an application against secure design principles such as Least Privilege and Defense in Depth. This case study ...

  • September 11 · 15 min

    Evaluate the Blog against the principles of secure design

    THEORETICAL RECAP Secure design principles are foundational rules that guide how an application should be architected to minimize attack surface and contain damage when a component is compromised. The core principles you must know include: Least Priv...

  • September 11 · 15 min

    Secure Design Principles — Least Privilege & Defense in Depth

    In the previous activities, you learned to identify threats using the STRIDE method, to draw Data Flow Diagrams, and to build a complete threat matrix for a Blog application. Those activities focused on finding and classifying threats. This activity ...

  • September 10 · 15 min

    Red thread — Building a complete threat matrix for the Blog

    Project Overview This mini-project is the culmination of the 'Application Security Principles and Threat Modeling' chapter. You will consolidate everything you have practiced so far — components/assets identification, CIA, STRIDE, Data Flow Diagrams ...

  • September 10 · 15 min

    Identify STRIDE threats in the DFD

    THEORETICAL RECAP Threat modeling connects two artifacts you have already built: the Data Flow Diagram (DFD) and the STRIDE taxonomy. A DFD represents your application as external entities (users, third parties), processes (services, APIs), data stor...

  • September 9 · 15 min

    Draw the DFD for the Blog application

    THEORETICAL RECAP A Data Flow Diagram (DFD) is a graphical model that shows how data moves through an application. It relies on four core symbols: external entities (rectangles) representing actors or systems outside your control (users, third-party ...

  • September 9 · 15 min

    Data Flow Diagram (DFD) — symbols and best practices

    A Data Flow Diagram, often abbreviated as DFD, is a visual representation of how information moves through an application or a system. In threat modeling, it is the foundation on which everything else is built. Before you can apply STRIDE, identify a...

  • September 8 · 15 min

    STRIDE on a “create post” API endpoint

    THEORETICAL RECAP STRIDE is a threat modeling framework that classifies threats into six categories: Spoofing (impersonating an identity), Tampering (altering data or code), Repudiation (denying an action without traceability), Information Disclosure...

  • September 7 · 15 min

    Apply STRIDE on the authentication flow

    THEORETICAL RECAP STRIDE is a threat classification model created by Microsoft that maps six threat categories to the security properties they violate: Spoofing (breaks Authentication), Tampering (breaks Integrity), Repudiation (breaks Non-repudiatio...

Showing 21–40 of 214 episodes