Episodios

  • Course 18 - Evading IDS Firewalls and Honeypots | Episode 1: Firewall Management and Security Testing: From Windows and Linux Configurations

    Course 18 - Evading IDS Firewalls and Honeypots | Episode 1: Firewall Management and Security Testing: From Windows and Linux Configurations
    Jan 14 2026
    In this lesson, you’ll learn about:
    • Firewall Fundamentals and Windows Configuration:
      • What a firewall is and how it mediates between network zones using rules based on source/destination addresses and ports.
      • Windows Firewall network profiles: Domain, Private, and Public.
      • Key practices:
        • Application Control: Allow specific programs, block vulnerable protocols like SMB/RPC on public networks.
        • Advanced Rules: Configure IPSec for authenticated/encrypted transmissions; set granular inbound/outbound rules.
        • Logging and Analysis: Use tools to convert large text logs into graphical summaries to detect anomalies.
    • Linux Firewall Management with IPTables:
      • IPTables chains: Input, Forward, and Output.
      • Key practices:
        • Block Traffic: Drop packets by source IP or destination port.
        • Advanced Filtering: Flood protection, limit concurrent SSH sessions, divert unauthorized Telnet traffic to a honeypot.
        • Audit Activity: Monitor dropped packets in system logs for attack analysis.
    • Advanced Rule Management and Verification:
      • Use GUI tools like Firewall Builder for Linux/Cisco (ASA/PIX) platforms to simplify rule creation and detect issues like “rule shadowing.”
      • Verify policies with Port Tester to ensure ports are open or blocked as intended.
    • Analogy for Understanding Firewalls:
      • Think of a firewall as a security team at a gated campus: rules dictate who enters (Input), moves between buildings (Forward), and exits with equipment (Output). Tools like Firewall Builder are blueprints to prevent conflicts, while port testing acts as surprise inspections to catch accidental backdoors.
    • Best Practices:
      • Apply proper configuration, audit logs, verify rules, and ensure security policies are effective across Windows and Linux environments.


    You can listen and download our episodes for free on more than 10 different platforms:
    https://linktr.ee/cybercode_academy
    Más Menos
    13 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 9: Foundations of VPN Security: The IPsec Protocol Suite

    Course 17 - Computer Network Security Protocols And Techniques | Episode 9: Foundations of VPN Security: The IPsec Protocol Suite
    Jan 13 2026
    In this lesson, you’ll learn about:
    • The fundamentals of VPNs and IPsec
    • Key management and Security Associations (SA)
    • IPsec protocols: AH vs. ESP
    • Operational modes: Transport vs. Tunnel
    1. VPNs and IPsec Fundamentals
    • A VPN (Virtual Private Network) creates a secure, logical tunnel over the public internet, allowing private communication without costly dedicated lines.
    • IPsec (Internet Protocol Security) operates at the network layer and supports both IPv4 and IPv6.
    • Security services provided by IPsec include:
      1. Access Control – Only authorized users can send/receive data
      2. Data Origin Authentication – Verify the source of the packet
      3. Integrity Protection – Ensure data hasn’t been tampered with
      4. Confidentiality – Encrypt the packet contents
      5. Anti-Replay – Detect and discard duplicated or malicious packets
    2. IPsec Framework and Key Management
    • Encryption algorithms: DES, 3DES, AES for confidentiality
    • Integrity algorithms: MD5, SHA to create digital signatures (MACs)
    • Key exchange: Diffie-Hellman ensures a shared secret is established securely
    3. Security Associations (SA) and IKE
    • An SA is a unidirectional logical connection, identified by:
      • SPI (Security Parameter Index)
      • Destination IP address
    • Bidirectional communication requires two SAs.
    • IKE (Internet Key Exchange) establishes SAs and manages keys:
      • IKE Phase 1: Creates a secure management tunnel (authenticates parties, negotiates algorithms, performs Diffie-Hellman exchange)
      • IKE Phase 2: Sets up the actual data tunnel (negotiates AH/ESP and operational mode)
    • IKEv2 is the modern version, supporting NAT traversal and keep-alive, and is widely used in 5G networks.
    4. IPsec Protocols: AH vs. ESPProtocolSecurity ProvidedNotesAH (Authentication Header)Integrity & authenticationDoes not encrypt; ignores changing IP header fields like TTLESP (Encapsulating Security Payload)Integrity, authentication, encryptionPreferred protocol for most VPNs and mandatory for 5G

    5. Operational Modes: Transport vs. Tunnel
    • Transport Mode: Only the payload is encrypted; original IP header is visible
    • Tunnel Mode: Entire original IP packet (header + payload) is encrypted inside a new IP packet
    • Most common setup: Tunnel Mode + ESP (encrypts everything and ensures privacy)
    Analogy:
    • Transport Mode: Transparent envelope with coded letter inside – address is visible, content protected
    • Tunnel Mode: Envelope inside an opaque crate – both content and sender/receiver are hidden


    You can listen and download our episodes for free on more than 10 different platforms:
    https://linktr.ee/cybercode_academy
    Más Menos
    13 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 8: TLS/SSL Foundations: From Conceptual "Toy" Models to Actual

    Course 17 - Computer Network Security Protocols And Techniques | Episode 8: TLS/SSL Foundations: From Conceptual "Toy" Models to Actual
    Jan 12 2026
    In this lesson, you’ll learn about:
    • The purpose and security objectives of TLS/SSL
    • How a simplified "Toy TLS" model illustrates key concepts
    • How actual TLS works, including handshake, key derivation, and record protocols
    • The role of cipher suites and secure data transfer
    1. Core Security Services of TLS/SSL TLS (Transport Layer Security) is designed to protect communications over insecure networks. Its four main security services are:
    1. Authentication – Verify the identities of client and server using digital certificates.
    2. Encryption – Protect data from being read by unauthorized parties.
    3. Integrity Protection – Detect any changes or tampering of transmitted data.
    4. Replay Attack Prevention – Stop attackers from resending valid data to repeat actions (like fraudulent payments).
    2. Toy TLS: A Conceptual Model The "Toy TLS" model is a simplified way to understand TLS: Handshake & Key Derivation
    • Step 1: Client (Alice) and server (Bob) authenticate each other with certificates.
    • Step 2: They exchange a master secret and nonces (random numbers).
    • Step 3: From the master secret, four keys are derived:
      • Two for encryption (one per direction)
      • Two for MAC (Message Authentication Code) to verify integrity
    Secure Data Transfer
    • Data is divided into records (frames).
    • Each record includes:
      • Length header – defines boundaries between data and MAC
      • MAC – ensures integrity and prevents tampering
    Advanced Protections
    • Sequence numbers prevent reordering attacks.
    • Type field in MAC prevents truncation attacks, where an attacker might cut off messages prematurely.
    3. Actual TLS Implementation Cipher Suites
    • TLS uses cipher suites to define:
      • Public key algorithm (e.g., RSA)
      • Symmetric encryption algorithm (e.g., AES, RC4)
      • Hash algorithm for MAC (e.g., SHA-256)
    • Client proposes supported suites; server chooses the strongest mutually supported one.
    Four-Step Handshake
    1. Negotiate security capabilities
    2. Server authenticates itself to the client
    3. Optional client authentication
    4. Finalization – premaster secret and session keys are derived using exchanged random numbers
    Record Protocol
    • Ensures secure data transfer by:
      1. Fragmenting the message
      2. Compressing the data
      3. Appending a MAC
      4. Encrypting the record
      5. Adding a TLS header (content type, version, length) before sending over TCP
    Analogy
    • Handshake: Like a secure diplomatic meeting where participants check IDs, agree on a secret language, and synchronize watches.
    • Record Protocol: The actual conversation, where each sentence is translated, numbered, and sealed so the listener can verify order and integrity.


    You can listen and download our episodes for free on more than 10 different platforms:
    https://linktr.ee/cybercode_academy
    Más Menos
    14 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 7: Understanding Pretty Good Privacy (PGP) for Secure Email

    Course 17 - Computer Network Security Protocols And Techniques | Episode 7: Understanding Pretty Good Privacy (PGP) for Secure Email
    Jan 11 2026
    In this lesson, you’ll learn about:
    • What PGP is and where it operates in the network stack
    • How PGP secures email confidentiality and authenticity
    • The three-part structure of a PGP-secured message
    • How session keys, public keys, and digital signatures work together
    • The cryptographic algorithms supported by PGP
    Introduction Pretty Good Privacy (PGP) is an application-layer security protocol designed to protect email communications. It combines symmetric encryption, public key cryptography, and digital signatures to ensure that messages remain confidential, authentic, and tamper-proof during transmission. How PGP Secures an Email PGP divides a protected email into three main components, each serving a specific security purpose. Part One: Session Key Protection
    • Contains the session key and the symmetric encryption algorithm used
    • The session key is a temporary, randomly generated key
    • This entire part is encrypted using the recipient’s public key
    • Ensures that only the intended recipient can recover the session key
    Part Two: Encrypted Content and Digital Signature
    • Contains the actual email message
    • The message is encrypted using the session key
    • Includes a digital signature created by:
      • Hashing the message to produce a digest
      • Encrypting the digest with the sender’s private key
    • Provides:
      • Integrity (message was not altered)
      • Authentication (message truly came from the sender)
      • Non-repudiation
    • Also specifies the hashing and encryption algorithms used
    Part Three: PGP Header
    • Contains protocol-related metadata
    • Helps the recipient’s PGP software correctly process the message
    Cryptographic Algorithms Supported by PGP PGP is flexible and supports multiple cryptographic standards:
    • Public Key Algorithms:
      • RSA
      • DSS
    • Hash Functions:
      • MD5
      • SHA-1
      • RIPEMD
    • Symmetric Encryption Algorithms:
      • AES
      • Triple DES (3DES)
    Key Takeaways
    • PGP operates at the application layer
    • Uses hybrid encryption for efficiency and security
    • Public keys protect the session key, not the message directly
    • Digital signatures ensure authenticity and integrity
    • Widely used for secure email communication


    You can listen and download our episodes for free on more than 10 different platforms:
    https://linktr.ee/cybercode_academy
    Más Menos
    11 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 6: The Evolution of End Point Authentication: Securing Identities

    Course 17 - Computer Network Security Protocols And Techniques | Episode 6: The Evolution of End Point Authentication: Securing Identities
    Jan 10 2026
    In this lesson, you’ll learn about:
    • What end point authentication is and why it matters
    • Why early authentication methods failed
    • How replay attacks and spoofing work
    • The role of nonces in proving “liveness”
    • Why public keys alone are not enough
    • How digital certificates solve Man-in-the-Middle attacks
    Introduction End point authentication is the process by which one entity proves its identity to another over a network. This lesson traces the evolution of authentication mechanisms, showing how each weak design led to stronger and more secure solutions used on today’s internet. 1. Early Authentication Methods and Their Failures Simple Identification & IP-Based Authentication
    • An entity simply claims an identity, or
    • Identity is inferred from the source IP address
    • Problem: Attackers can easily spoof IP addresses
    • Result: No real proof of identity
    Passwords and Encrypted Passwords
    • Users authenticate by sending a password (plain or encrypted)
    • Problem: Vulnerable to replay attacks
      • An attacker records the authentication packet
      • The same packet is resent later to gain access
    • Encryption does not prevent replay
    2. Nonces and Challenge–Response Authentication What Is a Nonce?
    • A random number used only once
    • Ensures the communicating party is “live”
    How It Works
    • Bob sends a nonce to Alice
    • Alice encrypts the nonce using a shared secret key
    • Bob decrypts and verifies the response
    Strengths
    • Prevents replay attacks
    • Proves the entity is actively responding
    Limitations
    • Requires a pre-shared secret key
    • Not scalable for large networks or the internet
    3. Public Key Authentication and Its Weakness Why Public Keys Were Introduced
    • Removes the need for pre-shared secrets
    • Anyone can encrypt data using a public key
    The Major Flaw: Man-in-the-Middle (MITM)
    • An attacker intercepts the communication
    • Substitutes their own public key
    • Alice and Bob each think they are talking directly
    • Attacker reads and modifies all traffic
    Key Insight
    • Public key cryptography alone does not authenticate identity
    4. The Final Solution: Digital Certificates What Digital Certificates Solve
    • Bind a public key to a verified identity
    • Prevent attackers from substituting keys unnoticed
    Role of Certification Authorities (CAs)
    • Verify identities
    • Issue digital certificates
    • Sign certificates using their private key
    Why This Stops MITM Attacks
    • An attacker cannot forge a valid certificate
    • Any key substitution attempt is detected
    • Trust is anchored in the CA
    5. Real-World Impact
    • This model is the foundation of HTTPS
    • Modern browsers automatically verify certificates
    • End point authentication is now built into everyday internet use
    Key Takeaways
    • Identity claims and IP-based authentication are insecure
    • Passwords alone are vulnerable to replay attacks
    • Nonces add freshness but require shared secrets
    • Public keys enable scalability but are MITM-prone
    • Digital certificates are the only robust solution
    • Trusted third parties are essential for secure authentication


    You can listen and download our episodes for free on more than 10 different platforms:
    https://linktr.ee/cybercode_academy
    Más Menos
    14 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 5: Digital Trust and Integrity: Hash Functions and Certification

    Course 17 - Computer Network Security Protocols And Techniques | Episode 5: Digital Trust and Integrity: Hash Functions and Certification
    Jan 9 2026
    In this lesson, you’ll learn about:
    • How data integrity is ensured using cryptographic hash functions
    • How MD5 and SHA-1 generate fixed-length message digests
    • Why encryption alone does not guarantee identity
    • How Certification Authorities (CAs) authenticate identities and prevent impersonation
    Introduction This lesson explains how secure digital communication relies on two critical pillars beyond encryption: integrity verification and identity authentication. It focuses on the role of hash functions in detecting data tampering and the role of Certification Authorities in establishing trust between communicating parties. 1. Data Integrity with Hash Functions Hash functions transform data of any size into a fixed-length output, known as a message digest. Even a one-bit change in the original message results in a completely different hash value. Key Properties of Hash Functions
    • Fixed-size output regardless of input size
    • One-way (computationally infeasible to reverse)
    • Highly sensitive to input changes
    • Efficient to compute
    MD5 (Message Digest 5)
    • Produces a 128-bit hash value
    • Processes data through multiple internal transformation rounds
    • Designed to make it infeasible to reconstruct the original message from the digest
    • Useful historically for integrity checks, though no longer considered secure against collisions
    SHA-1 (Secure Hash Algorithm 1)
    • Produces a 160-bit hash value
    • Standardized by NIST
    • Divides input into 512-bit blocks
    • Each block is processed sequentially
    • The output of one round becomes part of the input to the next
    • More robust than MD5, but now considered cryptographically weak for modern security needs
    Why Hash Functions Matter
    • Detect unauthorized changes to data
    • Ensure files and messages arrive unaltered
    • Used in digital signatures, password storage, and integrity verification
    2. Identity Authentication with Certification Authorities (CAs) Encryption protects confidentiality, but it does not prove who sent the message. Without authentication, attackers can impersonate legitimate users. The Problem: Impersonation An attacker can:
    • Claim to be someone else
    • Send their own public key while pretending it belongs to a trusted entity
    • Trick the recipient into trusting malicious communication
    The Solution: Certification Authorities Certification Authorities are trusted third parties that verify identities and bind them to cryptographic keys. What a CA Does
    • Verifies the identity of an individual or organization
    • Binds that identity to a public key
    • Issues a digital certificate
    • Signs the certificate using the CA’s private key
    How Certificates Are Used
    • The recipient verifies the certificate using the CA’s public key
    • The sender’s authentic public key is extracted from the certificate
    • This ensures:
      • The message truly came from the claimed sender
      • The message was not altered in transit
    How Integrity and Authentication Work Together
    • Hash functions detect message modification
    • Digital certificates confirm sender identity
    • Combined, they prevent:
      • Tampering
      • Spoofing
      • Man-in-the-Middle attacks
    Key Takeaways
    • Hash functions ensure data integrity, not identity
    • MD5 and SHA-1 produce fixed-length digests from variable-length input
    • Encryption alone cannot prevent impersonation
    • Certification Authorities establish trust by binding identities to public keys
    • Secure communication requires integrity + authentication + encryption


    You can listen and download our episodes for free on more than 10 different platforms:
    https://linktr.ee/cybercode_academy
    Más Menos
    11 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 4: Asymmetric Cryptography: RSA, Diffie-Hellman

    Course 17 - Computer Network Security Protocols And Techniques | Episode 4: Asymmetric Cryptography: RSA, Diffie-Hellman
    Jan 8 2026
    In this lesson, you’ll learn about:What asymmetric (public key) cryptography is and why it is neededHow the RSA algorithm works and where it is used in practiceHow Diffie-Hellman enables secure key exchange over public networksWhy asymmetric cryptography is vulnerable without authenticationIntroduction This lesson provides an in-depth explanation of asymmetric key cryptography, focusing on RSA and Diffie-Hellman. These algorithms solve a fundamental problem in network security: how to communicate securely over an insecure channel, such as the internet, without sharing secrets in advance. Asymmetric Cryptography Overview Asymmetric cryptography uses two mathematically related keys:Public key: Shared with everyonePrivate key: Kept secret by the ownerWhat is encrypted with one key can only be decrypted with the other. This model enables secure communication, authentication, and key exchange at scale. 1. RSA (Rivest–Shamir–Adleman) RSA is a general-purpose asymmetric encryption algorithm based on the computational difficulty of factoring very large numbers. Key GenerationTwo large prime numbers are selected: P and QThese are multiplied to produce n = P × QA public key is created: (n, e)A private key is created: (n, d)Knowing n does not make it feasible to derive d without factoring nEncryption and DecryptionThe sender converts the message into a number MEncryption is performed using the public key:C = M^e mod nThe receiver decrypts using the private key:M = C^d mod nOnly the private key holder can reverse the operation. Practical Use of RSARSA operations are slow and computationally expensiveIt is not used to encrypt large dataInstead, RSA is commonly used to:Securely exchange a symmetric session keyAuthenticate servers and usersThe exchanged symmetric key is then used with fast algorithms like AES2. Diffie-Hellman Key Exchange Diffie-Hellman is not an encryption algorithm; it is a key exchange protocol. PurposeAllows two parties to generate a shared symmetric keyNo prior secret is requiredThe shared key is never transmitted over the networkHow It WorksTwo public values are agreed upon:A large prime number PA generator GEach party chooses a private value:Alice chooses XBob chooses YPublic values are exchanged:Alice sends G^X mod PBob sends G^Y mod PBoth compute the same shared secret:G^(XY) mod PEven though all exchanged values are public, the shared secret remains secure. Key PropertiesSecure against passive eavesdroppingEnables perfect forward secrecy when used correctlyWidely used in secure protocols such as TLS3. Man-in-the-Middle (MITM) Vulnerability Both RSA and Diffie-Hellman are mathematically secure, but they are vulnerable at the protocol level if identities are not verified. The AttackAn attacker intercepts the key exchangeEstablishes one secret key with AliceEstablishes a different secret key with BobRelays messages between both sides while decrypting and re-encrypting themBoth parties believe they are communicating securely, but the attacker sees everything. The SolutionAuthentication is mandatoryIdentity verification must occur before or during key exchangeCommon solutions include:Digital certificatesTrusted certificate authoritiesSigned public keysWithout authentication, encryption alone does not guarantee security. Key TakeawaysAsymmetric cryptography solves the secure key distribution problemRSA relies on the difficulty of factoring large numbersRSA is mainly used for key exchange and authentication, not bulk data encryptionDiffie-Hellman enables secure key exchange without sharing secretsBoth systems are vulnerable to MITM attacks without authenticationSecure systems always combine encryption + authenticationYou can listen and download our episodes for free on more than 10 different platforms:https://linktr.ee/cybercode_academy
    Más Menos
    14 m
  • Course 17 - Computer Network Security Protocols And Techniques | Episode 3: Modern Ciphers: Structure, Standards (DES/AES)

    Course 17 - Computer Network Security Protocols And Techniques | Episode 3: Modern Ciphers: Structure, Standards (DES/AES)
    Jan 7 2026
    In this lesson, you’ll learn about:How modern cryptography differs from classical ciphersThe building blocks of bit-oriented encryptionHow DES, 3DES, and AES work at a high levelWhy block cipher modes of operation are necessaryIntroduction This lesson provides a structured overview of modern cryptographic techniques, focusing on how today’s encryption systems operate at the bit level, how complex standards like DES and AES are constructed, and how modes of operation securely apply block ciphers to real-world data. Foundational Concepts of Modern Ciphers Modern cryptography is bit-oriented, meaning it works directly on bits rather than characters. This allows encryption of all digital data types, including text, audio, images, and video. Basic Cipher Components Complex modern ciphers are built by combining several simple operations:XOR (Exclusive OR) CipherPerforms a bitwise XOR between data and a keySimple but essential for mixing key material with dataRotation CipherRotates bits left or right with wraparoundHelps spread bit influence across the dataSubstitution Ciphers (S-Boxes)Replace input bits with output bits using lookup tablesVariants include:Equal size substitution (n = m)Expansion (n < m)Compression (n > m)Transposition / Permutation Ciphers (P-Boxes or T-Boxes)Reorder bits based on fixed permutation patternsCan preserve size or perform expansion/reductionIncrease diffusion by spreading bit changesRound Cipher Structure Most modern block ciphers use a round-based design:Encryption is performed over multiple roundsEach round applies substitution, permutation, and XOREach round uses a different subkey derived from a master keySecurity increases with the number and complexity of roundsKey Encryption Standards Data Encryption Standard (DES)Early U.S. encryption standardOperates on 64-bit blocksUses a 56-bit key (stored as 64 bits)Consists of 16 roundsDES Round Function Each round includes:Splitting input into two 32-bit halvesExpansion P-box: 32 → 48 bitsXOR with a 48-bit round keyS-boxes: 48 → 32 bitsStraight permutationFeistel structure swaps halves each roundTriple DES (3DES)Designed to improve DES securityApplies DES three times in an Encrypt–Decrypt–Encrypt sequenceKey options:Two-key version: 112-bit securityThree-key version: 168-bit securityMore secure than DES, but slower and largely deprecatedAdvanced Encryption Standard (AES)Current global encryption standardReplaced DES and 3DESOperates on 128-bit blocksSupports three key sizes:128-bit192-bit256-bitMore rounds are used as key size increasesDesigned for high security and high performanceModes of Operation for Block Ciphers Block ciphers encrypt fixed-size blocks, but real data streams require modes of operation to handle multiple blocks securely. 1. Electronic Code Book (ECB)Each block encrypted independentlyIdentical plaintext blocks → identical ciphertext blocksLeaks patterns and is insecureNot recommended for real-world use2. Cipher Block Chaining (CBC)Each plaintext block is XORed with the previous ciphertextEliminates repeated ciphertext patternsRequires an Initialization Vector (IV)Suffers from error propagation across blocks3. Cipher Feedback (CFB)Converts block cipher into a stream-like cipherSupports encrypting smaller data units (R bits)Uses a shift register with feedback from ciphertextError propagation affects subsequent blocks4. Output Feedback (OFB)Similar to CFB but feeds back encrypted output instead of ciphertextEncryption stream is independent of ciphertextNo error propagationRequires careful IV synchronizationInitialization Vector (IV)Required for CBC, CFB, and OFB modesEnsures uniqueness of the first encryption blockMust be agreed upon by sender and receiverPrevents pattern reuse across messagesKey TakeawaysModern encryption operates at the bit levelStrong ciphers are built from simple operations combined over many roundsDES introduced round-based block encryption but is no longer secure3DES improved security but is inefficientAES is the modern standard due to strength and performanceModes of operation are essential for securely encrypting large or streaming dataECB is insecure, while CBC, CFB, and OFB address pattern leakage in different waysYou can listen and download our episodes for free on more than 10 different platforms:https://linktr.ee/cybercode_academy
    Más Menos
    15 m
adbl_web_global_use_to_activate_DT_webcro_1694_expandible_banner_T1