InfoSec Bites

HelloInfoSec
  • 1,0 (1)
  • Технологии

Welcome to Hello InfoSec, your ultimate hub for all things cybersecurity! Dive into our thrilling podcast series, InfoSec Bites, where we unleash deep dives into Information Security, jaw-dropping Major Security Incidents, cutting-edge Cloud Information Security, crucial Privacy topics, revolutionary Artificial Intelligence, mind-bending Quantum Computing, and so much more! Get ready to geek out with expert insights and stay ahead of the curve—hit that like button, subscribe now, and turn on notifications for fresh episodes that will blow your mind! https://www.youtube.com/@HelloInfoSec

  1. 23 авг.

    ISO/IEC 27018: Guidelines for Protecting PII in Public Clouds

    ISO/IEC 27018 is the first international standard specifically designed to protect personally identifiable information (PII) in public cloud environments, acting as a specialized privacy extension to the foundational ISO/IEC 27001 Information Security Management System (ISMS). Tailored uniquely for cloud service providers (CSPs) acting as contractual PII processors, it translates the eleven privacy principles of ISO/IEC 29100 into concrete, cloud-native operational controls. The standard establishes strict technical and organizational accountability throughout the cloud data lifecycle, enforcing robust mechanisms for sub-processor transparency, geographical data residency disclosures, granular access controls, and automated tenant data purging. The standard's 2025 third edition modernized this framework, abandoning the legacy 18-section format of the 2019 version to align directly with the four-theme taxonomy—Organizational, People, Physical, and Technological controls—of ISO/IEC 27002:2022. While voluntary, implementing these guidelines provides a robust technical blueprint that helps cloud processors demonstrate compliance with prescriptive, legally binding regulations such as GDPR Article 28.

    ISO/IEC 27018: Guidelines for Protecting PII in Public Clouds

  2. 23 июл.

    The Silent Layer: Unmasking Container Base OS Security in AWS Environments

    This podcast discussion provides a technical deep dive into AWS Bottlerocket, a Linux-based, open-source operating system purpose-built by Amazon Web Services to host containerized workloads. Unlike general-purpose distributions that include thousands of packages, Bottlerocket follows a minimalist philosophy, stripping away package managers, scripting interpreters, and interactive shells to reduce the attack surface by approximately 60%. The architecture is rooted in immutability and defense-in-depth security. It enforces a read-only root filesystem verified through cryptographic digests (dm-verity) at boot, which prevents unauthorized runtime modifications and detects rootkit-based attacks. Security is further bolstered by SELinux in enforcing mode by default, kernel lockdown mechanisms, and support for hardware-based trusted computing. Operationally, Bottlerocket replaces traditional package-by-package updates with an atomic, image-based update model using A/B partitions. This mechanism enables single-step rollouts and rollbacks, eliminates "patch drift," and reduces update-related downtime by up to 80%. Performance benchmarks indicate superior efficiency, with faster node startup times (averaging under 39 seconds) and a 45% smaller memory footprint compared to traditional Linux environments. Management is handled through a secure, API-first approach. Direct host access is restricted; instead, administrative tasks are performed via isolated control and admin containers. The OS is optimized for major orchestrators like Amazon EKS and ECS, and it includes specialized variants for high-performance tasks, such as NVIDIA GPU-accelerated AI and machine learning workloads. Finally, the discussion explores Bottlerocket's role in meeting strict regulatory requirements. It is CIS hardened out-of-the-box, supports FIPS 140-3 validated cryptographic modules, and provides the architectural foundation for achieving PCI DSS compliance in cloud-native environments.

    The Silent Layer: Unmasking Container Base OS Security in AWS Environments

  3. 16 июл.

    Web Application Attacks & Adversarial Lifecycle: From Passive OSINT to Lateral Movement and Multi-Layered Detection

    Modern cybersecurity operations prioritize multi-layered reconnaissance, moving from passive OSINT gathering using tools like Amass and crt.sh to active verification via port profiling and directory enumeration. This initial phase aims to map the organization's external digital footprint, identifying exposed assets such as misconfigured subdomains, cloud storage buckets, and leaked credentials within public repositories. Once the attack surface is defined, adversaries leverage vulnerabilities like Server-Side Request Forgery (SSRF), SQL injection, and insecure deserialization to establish initial access and harvest temporary credentials from infrastructure metadata services. Following initial compromise, threat actors attempt privilege escalation through techniques such as "Potato-class" token impersonation or abusing overly permissive AWS IAM policies, often utilizing advanced agentic analysis frameworks for detection in complex polyglot microservices. Attackers then navigate the internal network via lateral movement, employing native tools like PsExec, PowerShell, and WMI while attempting to evade detection through credential dumping or token manipulation. Defending against these evolving threats requires a robust architecture that integrates NIST SP 800-61 incident handling guidelines with proactive measures like virtual patching, Web Application Firewalls (WAF), and the principle of least privilege. Furthermore, emerging technologies, including AI-driven log analysis and predictive shielding, enhance detection accuracy and enable real-time disruption of critical attack paths before a full domain compromise occurs.

    Web Application Attacks & Adversarial Lifecycle: From Passive OSINT to Lateral Movement and Multi-Layered Detection

  4. 9 июл.

    Authentication and Authorisation bypass: The Invisible Threat

    Access control serves as a foundational security framework divided into authentication, which verifies identity, and authorization, which regulates interaction boundaries between active subjects and passive resources. Despite its criticality, broken access control remains a top vulnerability, frequently exploited through mechanics such as Insecure Direct Object References (IDOR), parameter tampering, and architectural decoupling that allow attackers to bypass identity checks or escalate privileges. Modern technical shifts toward cloud-native systems, microservices, and AI agents have significantly expanded this attack surface, introducing complex failure modes like "Golden SAML" token forgery and task boundary drift, where legitimate sessions are manipulated to perform unauthorized actions. To mitigate these pervasive risks, enterprises must move beyond traditional perimeter defenses and adopt a Zero Trust posture centered on Attribute-Based Access Control (ABAC), the principle of least privilege, and continuous behavioral monitoring to detect the subtle logic flaws and design gaps that automated scanners often miss.

    Authentication and Authorisation bypass: The Invisible Threat

  5. 2 июл.

    Remote Code Execution: Vulnerability Mechanics, Mitigation Bypassing, and Defensive Architecture

    Remote Code Execution (RCE) represents the highest tier of security compromise, enabling unauthorized attackers to execute arbitrary commands or machine code on a system over a network boundary. These flaws reflect a fundamental failure to isolate untrusted data from the CPU’s instruction registers, effectively subverting the standard security boundaries of the Von Neumann execution model. The mechanics of RCE vary across runtime environments: native applications written in C or C++ are primarily vulnerable to memory corruption flaws, such as stack-based buffer overflows that overwrite return pointers to redirect execution. Conversely, managed environments like the Java Virtual Machine or Python typically experience RCE through high-level logic failures, including insecure deserialization—where "gadget chains" trigger commands during object reconstruction—or web framework exploits like OGNL injection and Server-Side Template Injection (SSTI) that manipulate internal evaluation engines. The impact of a successful RCE exploit is often catastrophic, leading to full system compromise, privilege escalation, and the lateral movement of attackers throughout an entire network. Landmark crises such as Log4Shell, EternalBlue, and the Apache Struts breach illustrate how these vulnerabilities facilitate massive data exfiltration and the automated propagation of ransomware like WannaCry. While defensive measures such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and stack canaries provide initial protection, attackers frequently bypass these using advanced techniques like Return-Oriented Programming (ROP) and memory leakage. Building a resilient architecture requires a defense-in-depth strategy that combines rapid patch management, strict input validation, the principle of least privilege, and network egress filtering to disrupt the multi-stage exploitation lifecycle.

    Remote Code Execution: Vulnerability Mechanics, Mitigation Bypassing, and Defensive Architecture

  6. 25 июн.

    Modernising Vulnerability Prioritisation via CISA KEV and BOD 26-04

    The discussion in this podcast examines CISA’s Known Exploited Vulnerabilities (KEV) catalog and its evolving role in national cybersecurity policy. This authoritative registry identifies security flaws with confirmed evidence of active exploitation and clear remediation paths, serving as a critical tool for prioritizing defensive actions. Recent updates, specifically Binding Operational Directive (BOD) 26-04, move away from traditional severity scores toward a risk-based decision tree that mandates remediation in as little as three days for high-exposure assets. While these directives primarily govern federal agencies, the KEV catalog has become a de facto global benchmark for private industries, insurers, and medical device manufacturers. The discussion further compares this confirmed exploitation data with predictive models like the Exploit Prediction Scoring System (EPSS) to help organizations anticipate future threats. Collectively, we highlight a shift toward automated, evidence-driven vulnerability management to counter the speed of modern, AI-assisted cyberattacks.

    Modernising Vulnerability Prioritisation via CISA KEV and BOD 26-04

  7. 18 июн.

    Decoding NIST CSWP 41: Predicting Vulnerability Exploitation Metrics

    The discussion in this podcast covers the introduction of the Likely Exploited Vulnerabilities (LEV) metric, proposed in NIST Cybersecurity White Paper 41 by Peter Mell and Jonathan Spring to address a critical gap in the "remediation deficit" where organizations can typically only patch a small fraction of annual CVEs. LEV functions as a retrospective, probabilistic score that compounds historical Exploit Prediction Scoring System (EPSS) data to estimate the cumulative likelihood that a vulnerability has already been exploited in the past, thereby correcting the "past-exploitation blindness" of forward-looking models. The metric is designed to complement rather than replace existing frameworks, offering use cases for measuring the comprehensiveness of the CISA Known Exploited Vulnerabilities (KEV) catalog and enhancing prioritization through a Composite Probability score—defined as the maximum signal of EPSS, LEV, and KEV. Technical advancements discussed alongside these metrics include the FORGE multi-agent system for automated exploit generation and Bayesian Network models for real-time, adaptive decision support in critical infrastructure. Despite its mathematical utility, the LEV framework has prompted significant industry debate regarding its "independent events" assumption, the validity of its LEV2 daily-linear approximation, and the risk of "triage inflation" by permanently elevating the priority of dormant legacy threats. Collectively, the discussion highlight a strategic shift toward evidence-driven exposure management and rigorous operational mandates, such as CISA BOD 26-04, which requires federal agencies to prioritize remediation based on active threat telemetry and forensic compromise checks.

    Decoding NIST CSWP 41: Predicting Vulnerability Exploitation Metrics

  8. 11 июн.

    EPSS: Leveraging the Exploit Prediction Scoring System (EPSS) to Reduce Remediation Workloads

    The discussion in this podcast about paradigm shift in cybersecurity from traditional, static vulnerability management centered on the Common Vulnerability Scoring System (CVSS) toward dynamic, risk-based prioritization models that integrate global threat intelligence with local business context. This evolution is driven by an exponential surge in vulnerability disclosures—surpassing 25,000 annually and continuing to climb—which has created a critical crisis of alert fatigue and cognitive overload for security operations teams. Central to this transition are data-driven tools like the Exploit Prediction Scoring System (EPSS), which uses machine learning to forecast the 30-day probability of exploitation activity, and the CISA Known Exploited Vulnerabilities (KEV) catalog, which provides high-confidence validation of active threats. Modern research advocates for Vulnerability Management Chaining (VMC) and integrated frameworks that layer these global signals with asset criticality, reachability, and exposure to filter out the "noise" of non-exploitable vulnerabilities; evaluations of these methods show they can reduce urgent remediation workloads by up to 95% while maintaining over 85% threat coverage. Ultimately, the sources emphasize that while global scoring systems provide essential "pre-threat intelligence," effective exposure management requires local calibration, AI-powered autonomous investigation, and a broader industry move toward secure-by-design principles to address the increasingly fragmented attack surface of hybrid cloud environments.

    EPSS: Leveraging the Exploit Prediction Scoring System (EPSS) to Reduce Remediation Workloads
См. все (155)

Оценки и отзывы

Об этом подкасте

Welcome to Hello InfoSec, your ultimate hub for all things cybersecurity! Dive into our thrilling podcast series, InfoSec Bites, where we unleash deep dives into Information Security, jaw-dropping Major Security Incidents, cutting-edge Cloud Information Security, crucial Privacy topics, revolutionary Artificial Intelligence, mind-bending Quantum Computing, and so much more! Get ready to geek out with expert insights and stay ahead of the curve—hit that like button, subscribe now, and turn on notifications for fresh episodes that will blow your mind! https://www.youtube.com/@HelloInfoSec

Информация

  • Автор
    HelloInfoSec
  • Годы выхода
    2025 - 2026
  • Выпуски
    155
  • Ограничения
    Без ненормативной лексики
  • Авторские права
    © HelloInfoSec
  • Сайт подкаста
    InfoSec Bites