Certified: The CompTIA Security+ V8 / SY0-801 Audio Course
Jason Edwards 119 episodes Apr 26, 2026
This podcast is an audio-first study course for the CompTIA Security+ V8 / SY0-801 exam, aimed at entry-level security professionals, IT support staff, junior administrators, and career changers. Each lesson explains exam objectives in plain language and connects them to decisions security teams make in practice. Topics include threats and vulnerabilities, secure architecture, identity and access management, cryptography, risk and governance, incident response, cloud security, endpoint protection, and operational security. The format is designed to be listened to while driving, walking, exercising, or reviewing between other responsibilities rather than read from slides.
Episodes
Episode 1 — SY0-801 at a Glance: What Changed from Security+ 701
This episode introduces the SY0-801 version of Security+ by explaining how the exam direction moves beyond traditional baseline security topics into modern cloud operations, identity-centered security, AI-related risk, automation, and practical security operations. For exam preparation, the focus is on understanding how the draft 801 objectives organize security knowledge into decisions a
Episode 2 — How to Study with an Audio-First Security+ Plan
This episode explains how to use an audio-first study plan to build recall, reinforce weak areas, and connect exam objectives to practical security scenarios. For Security+ preparation, short lessons are most useful when students listen by domain, revisit topics that feel unclear, and actively ask what decision they would make in a real environment. The episode covers spaced repetition, s
Episode 3 — Defense in Depth: Layering Controls So One Failure Doesn’t Sink You (1.1)
This episode explains defense in depth as the practice of using multiple overlapping controls so a single failure does not expose the entire organization. For the exam, students should recognize how administrative, technical, physical, and operational safeguards work together across people, process, and technology. Examples include multifactor authentication protecting accounts, endpoint
Episode 4 — CIA and AAA: The Core Security Models (1.1)
This episode covers two foundational security models that appear throughout Security+: CIA and AAA. Confidentiality protects information from unauthorized access, integrity protects information from unauthorized or improper change, and availability ensures systems and data remain usable when needed. Authentication verifies identity, authorization determines what that identity is allowed t
Episode 5 — Non-Repudiation, Least Privilege, and Trust Decisions (1.1)
This episode explains non-repudiation, least privilege, and trust decisions as core principles behind secure design and accountability. Non-repudiation means there is evidence that an action, transaction, or message came from a specific party and cannot easily be denied later, often through digital signatures, logs, and strong identity controls. Least privilege means users, services, and
Episode 6 — Zero Trust Principles: Never Trust, Always Verify (1.1)
This episode introduces Zero Trust as a security model based on continuous verification, least privilege, and the assumption that compromise may already exist inside or outside the network. For the exam, students should understand that Zero Trust is not a single product but an approach to evaluating every access request using identity, device posture, location, application sensitivity, be
Episode 7 — Control Categories and Control Types (1.1)
This episode explains how security controls are grouped by category and by function, which is a common Security+ exam pattern. Technical controls use systems or tools, managerial controls guide planning and oversight, operational controls are performed through processes and people, and physical controls protect facilities and equipment. Control types describe what the control does: preven
Episode 8 — Change Management: Why Security Breaks During Normal Updates (1.2)
This episode explains why normal system changes can create security problems even when no attacker is involved. For Security+ preparation, change management should be understood as a risk control process that reduces outages, misconfigurations, control failures, and newly introduced vulnerabilities. Examples include a firewall rule that exposes a service, a patch that breaks authenticatio
Episode 9 — CABs, Approvals, Ownership, and Stakeholders (1.2)
This episode covers the people and approval structures that help manage change risk, including change advisory boards, change owners, technical approvers, business stakeholders, and affected teams. For the exam, students should understand that approvals are not just bureaucracy; they ensure the right people review downtime, security impact, dependencies, business timing, and recovery plan
Episode 10 — Impact Analysis, Test Results, and Maintenance Windows (1.2)
This episode explains how impact analysis, testing, and maintenance windows reduce the security and operational risk of production changes. Impact analysis identifies affected systems, dependencies, users, data, controls, downtime expectations, and possible security consequences before implementation. Test results provide evidence that a patch, configuration change, firewall rule, or appl
Episode 11 — Backout Plans vs. Fail Forward: Recovering from Bad Changes (1.2)
This episode explains two common recovery strategies used when a change causes problems: backing out and failing forward. A backout plan returns the environment to a known-good state, such as restoring a prior firewall rule set, reverting an application version, or removing a failed patch. Failing forward means applying an additional fix to stabilize the environment without returning to t
Episode 12 — Technical and Documentation Impacts of Change (1.2)
This episode covers the technical and documentation effects that often follow a change, especially when security controls, access rules, or system dependencies are modified. Students should understand how allow lists, deny lists, restricted activities, restarts, downtime, legacy applications, and dependency issues can affect normal operations and security posture. A change may require upd
Episode 13 — PKI Foundations: Public Keys, Private Keys, and Trust (1.3)
This episode introduces public key infrastructure as a trust system that supports encryption, authentication, digital signatures, and secure communication. Public keys can be shared, while private keys must be protected because they prove identity, decrypt protected information, or create signatures. The exam expects students to understand that PKI depends on key pairs, certificates, cert
Episode 14 — Certificates and Certificate Authorities (1.3)
This episode explains what digital certificates prove and how certificate authorities help establish trust between systems, users, applications, and websites. A certificate binds an identity to a public key, allowing other parties to validate that they are communicating with the expected entity. Students should understand the difference between third-party certificates trusted by common d
Episode 15 — Revocation and Validation: CRLs, OCSP, and Trust Problems (1.3)
This episode explains why certificates sometimes must be revoked before their normal expiration date and how systems check whether a certificate should still be trusted. A certificate may be revoked because a private key was compromised, the certificate was issued incorrectly, the owner changed, or the service no longer exists. Students should recognize certificate revocation lists and th
Episode 16 — CSRs, Wildcards, Root of Trust, and Key Escrow (1.3)
This episode covers certificate signing requests, wildcard certificates, root of trust concepts, and key escrow. A certificate signing request is generated when an organization wants a certificate authority to issue a certificate for a public key and identity. Wildcard certificates can secure multiple subdomains but increase impact if the private key is compromised. The root of trust is t
Episode 17 — Symmetric vs. Asymmetric Encryption (1.3)
This episode compares symmetric and asymmetric encryption by focusing on how each method is used in practical security designs. Symmetric encryption uses the same secret key to encrypt and decrypt data, making it fast and useful for files, disks, databases, and bulk traffic protection. Asymmetric encryption uses a public key and private key pair, making it useful for trust, secure key exc
Episode 18 — Encryption Levels: Disk, File, Volume, Database, and Record (1.3)
This episode explains where encryption can be applied and what each level protects. Full-disk encryption protects an entire drive when a device is powered off or stolen, while volume or partition encryption protects selected storage areas. File-level encryption protects individual files, database encryption protects stored database content, and record-level encryption can protect specific
Episode 19 — Key Exchange, Algorithms, Key Length, and Protocol Selection (1.3)
This episode covers how systems agree on encryption keys, choose algorithms, and select protocols without exposing sensitive material directly. Key exchange allows two parties to establish shared session protection even when communicating over an untrusted network. Algorithm choice and key length affect security strength, performance, compatibility, and resistance to attack. Students shou
Episode 20 — Hashing, Salting, Digital Signatures, Obfuscation, and Crypto Tools (1.3)
This episode explains several cryptographic concepts that are often confused on the exam. Hashing creates a fixed output used to verify integrity, while salting adds unique random data before hashing passwords to make precomputed attacks harder. Digital signatures support authentication, integrity, and non-repudiation by proving that data was signed with a private key and has not been alt
Episode 21 — Threats vs. Vulnerabilities: Likelihood, Impact, and Life Cycle (2.1)
This episode explains the difference between a threat, a vulnerability, and risk, which is essential for understanding Security+ scenarios. A threat is something that could cause harm, a vulnerability is a weakness that could be exploited, and risk combines likelihood with impact. Students should understand that a vulnerable system is not automatically the highest priority unless there is
Episode 22 — Threat Feeds and Intelligence Sources (2.1)
This episode covers threat feeds and intelligence sources as tools that help security teams understand which threats matter most. Students should recognize sources such as advisories, vendor reports, information-sharing groups, open-source intelligence, commercial feeds, internal telemetry, and security research. For the exam, the key idea is that intelligence supports prioritization by a
Episode 23 — Vulnerability Scoring: CVSS, CVEs, and Prioritization (2.1)
This episode explains CVEs and CVSS as common tools for identifying and scoring vulnerabilities. A CVE is a public identifier for a known vulnerability, while CVSS provides a scoring method that helps describe severity using factors such as exploitability, impact, complexity, and required privileges. For Security+ questions, students should remember that a high CVSS score does not always
Episode 24 — Vulnerability Types and Risk-Based Decisions (2.1)
This episode covers common vulnerability types across software, configuration, identity, cloud, and operational processes. Students should recognize that vulnerabilities may come from missing patches, insecure defaults, exposed services, weak passwords, excessive permissions, flawed code, misconfigured storage, unsupported systems, or poor procedures. For the exam, the goal is to connect
Episode 25 — Threat Actors: Organized Crime, Terrorists, Hacktivists, and Insiders (2.2)
This episode introduces major threat actor categories and explains how their goals and behavior differ. Organized crime groups often pursue financial gain through fraud, ransomware, data theft, and extortion. Terrorist actors may seek disruption, fear, attention, or damage to critical services. Hacktivists usually act from ideological or political motivation, using attacks to embarrass, d
Episode 26 — State-Sponsored, Competitors, Accidental, and Unskilled Attackers (2.2)
This episode explains additional threat actor types, including state-sponsored actors, competitors, accidental users, and unskilled attackers. State-sponsored actors may have funding, patience, specialized tools, and long-term intelligence or disruption goals. Competitors may seek business advantage through espionage, data theft, or unethical information gathering. Accidental users create
Episode 27 — Motivations and Capabilities: Money, Espionage, Ideology, and Extortion (2.2)
This episode connects attacker motivations to tactics, target selection, persistence, and expected impact. Financially motivated attackers may focus on ransomware, payment fraud, credential theft, or data resale. Espionage-driven attackers may seek intellectual property, government information, business strategy, or sensitive communications. Ideological attackers may deface sites, leak da
Episode 28 — APTs and the Modern Threat Vector Map (2.3)
This episode introduces advanced persistent threats and uses them as a bridge into the broader Security+ threat vector landscape. An advanced persistent threat is typically associated with capable actors who use stealth, patience, planning, and repeated access attempts to achieve long-term objectives. For the exam, students should understand that persistence and quiet access can matter as
Episode 29 — Message-Based Attacks: Email, SMS, RCS, IM, and Collaboration Tools (2.3)
This episode covers message-based attacks delivered through email, SMS, Rich Communication Services, instant messaging, and collaboration platforms. Students should understand that attackers target the communication channels users already trust, especially when those channels support links, attachments, identity cues, urgency, and quick responses. Exam scenarios may include phishing email
Episode 30 — Image and Attachment Attacks: QR Codes, CAPTCHA Abuse, Macros, PDFs, and RTF (2.3)
This episode explains how attackers use familiar images and file types to deliver malicious content or manipulate user trust. QR-code attacks can move users from a protected screen to a malicious site on a personal device. CAPTCHA abuse may make a fraudulent page look more legitimate or delay automated analysis. Macros, PDFs, and RTF documents can contain embedded content, scripts, links,
Episode 31 — Browser-Based Attacks: Extensions, JavaScript, Cookies, Password Managers, and Session Tokens (2.3)
This episode explains why the browser is a major attack surface in modern environments and how attackers target the tools users rely on every day. Students should understand how malicious browser extensions can collect data, inject content, or abuse permissions, while JavaScript can be used for malicious redirects, credential theft, or exploitation of vulnerable web applications. Cookies
Episode 32 — Network, Remote Access, and Endpoint Threat Sources (2.3)
This episode covers threat sources connected to infrastructure devices, virtualized systems, session keys, remote desktop, VNC, VPNs, mobile devices, servers, tablets, trusted devices, and built-in administrative tools. For the exam, students should recognize that attackers often target normal access paths rather than using unusual traffic that is easy to detect. Remote access services ca
Episode 33 — Supply Chain, SaaS, USB, Human, IoT, OT, Physical, Bluetooth, RF, and NFC Threats (2.3)
This episode explains how attack paths often begin outside an organization’s directly managed systems. Students should understand supply chain risks involving third-party providers, managed service providers, logistics providers, SaaS platforms, contractors, and visitors. The episode also covers malicious USB devices, IoT devices, operational technology, physical access, Bluetooth, radio
Episode 34 — Unsupported, Unpatched, Obsolete, and Unmanaged Systems (2.4)
This episode explains why unsupported, unpatched, obsolete, and unmanaged systems create serious attack surface risk. Unsupported systems may no longer receive security updates, unpatched systems may remain vulnerable to known exploits, obsolete systems may rely on weak protocols or outdated dependencies, and unmanaged systems may be invisible to normal monitoring and inventory processes.
Episode 35 — Ports, Services, Applications, Race Conditions, and Malicious Updates (2.4)
This episode covers several common sources of technical exposure, including open ports, unnecessary services, vulnerable applications, race conditions, time-of-check/time-of-use weaknesses, and malicious updates. Students should understand that attackers look for services that should not be exposed, applications that are poorly maintained, and timing flaws that allow an action to change b
Episode 36 — Code Weaknesses: Hardcoded Secrets and Unsafe Exception Handling (2.4)
This episode explains two code-level weaknesses that frequently create preventable security problems: hardcoded secrets and unsafe exception handling. Hardcoded passwords, API keys, tokens, certificates, and database credentials are dangerous because they may be exposed through repositories, logs, backups, shared scripts, compiled applications, or insider access. Unsafe exception handling
Episode 37 — Stale Credentials, Rogue Devices, Shadow IT, Wireless, Mobile, and Identity Provider Risks (2.4)
This episode covers attack surface risks created by unmanaged identities, unmanaged assets, and uncontrolled technology use. Stale credentials remain active after users change roles, leave the organization, or stop using a service, creating opportunities for unauthorized access. Rogue devices and shadow IT bypass normal approval, monitoring, patching, and configuration standards. Wireless
Episode 38 — LLMs, Misconfigurations, Public Repositories, and Public Object Storage (2.4)
This episode explains newer and common attack surfaces involving large language models, cloud misconfigurations, exposed repositories, leaked secrets, and public object storage. Students should understand that LLMs become riskier when they are connected to sensitive data, business workflows, plugins, code execution, or internal systems. Misconfigured cloud resources can expose storage buc
Episode 39 — Malware Indicators: Ransomware, Trojans, Worms, Spyware, and Fileless Malware (2.5)
This episode covers common malware indicators and what they may reveal during detection or investigation. Ransomware may produce encryption notices, renamed files, inaccessible data, or unusual backup deletion attempts. Trojans may appear as legitimate software while creating hidden access, worms may spread automatically, spyware and keyloggers may collect sensitive information, and rootk
Episode 40 — Physical and Network Attack Indicators (2.5)
This episode explains indicators associated with physical and network attacks and how evidence may appear across different sources. Physical attack indicators include tailgating, shoulder surfing, skimming, forced entry, missing equipment, access badge anomalies, and surveillance footage that shows unauthorized presence. Network attack indicators may include DDoS traffic spikes, downgrade
Episode 41 — Social Engineering Indicators: Smishing, Vishing, Whaling, Quishing, and Deepfakes
This episode explains social engineering indicators across message, voice, executive-targeted, QR-code, impersonation, and synthetic media attacks. Students should understand smishing as phishing through text messages, vishing as voice-based deception, whaling as targeting senior leaders, quishing as using QR codes to send users to malicious destinations, and deepfakes as manipulated audi
Episode 42 — Indicators of Compromise: Hashes, Domains, Timestamps, Log Manipulation, and Impossible Travel
This episode covers indicators of compromise as clues that help analysts connect events to malicious activity. Students should understand how hashes can identify known suspicious files, IP addresses and domains can reveal command-and-control or phishing infrastructure, malicious processes can show execution, and file system artifacts can show persistence or staging. Timestamps help recons
Episode 43 — Application Attacks: Injection, Buffer Overflow, Replay, Privilege Escalation, Forgery, and Traversal
This episode explains common application attack indicators and what attackers are trying to accomplish when they exploit application weaknesses. Injection attacks attempt to send untrusted input that changes how a command, query, or interpreter behaves. Buffer overflows attempt to write more data than memory can safely hold, potentially causing crashes or code execution. Replay attacks re
Episode 44 — Credential Attacks: Password Spraying, Brute Force, User Enumeration, and MFA Bypass
This episode covers credential attack patterns and how they differ in visibility, speed, and detection. Password spraying uses a small number of common passwords across many accounts to avoid lockouts, while brute force attacks try many password combinations against one or more accounts. User enumeration attempts to discover valid usernames through login messages, timing differences, pass
Episode 45 — AI Threats: Model Manipulation, Poisoning, and Prompt Injection
This episode introduces AI security threats at a Security+ level, focusing on how attackers may manipulate models, poison data, or use prompt injection to influence outputs. Model manipulation can involve attempts to change behavior, extract sensitive information, or cause unsafe responses. Poisoning can affect training data, reference data, retrieval sources, or business content used by
Episode 46 — AI Failure Risks: Data Loss, Bias, Explainability, Hallucinations, and Ethics
This episode explains AI risks that can occur even when there is no traditional attacker. Data loss may happen when sensitive information is entered into tools, retained improperly, or exposed through connected systems. Bias can lead to unfair or unreliable outcomes, while poor explainability makes it difficult to understand why a system produced a result. Hallucinations occur when AI gen
Episode 47 — AI Abuse: Jailbreaking, Evasion, Privacy, Session Hijacking, and Code Execution
This episode covers ways AI-enabled systems can be abused when boundaries, permissions, or integrations are weak. Jailbreaking attempts to bypass safety or policy restrictions, while evasion attempts to avoid detection or filtering. Privacy exposure can occur when sensitive prompts, outputs, logs, or connected data sources are mishandled. Session hijacking becomes a concern when an attack
Episode 48 — Architecture Models: Cloud, On-Premises, Hybrid, Private, Public, and Community Cloud
This episode compares major architecture and deployment models and the security responsibilities each creates. On-premises environments usually give the organization more direct control over hardware, networks, and physical access, but also more operational responsibility. Public cloud offers scalability and managed services, private cloud provides dedicated resources, hybrid models combi
Episode 49 — Serverless, Multicloud, and Infrastructure as Code
This episode explains serverless computing, multicloud environments, and infrastructure as code as modern architecture concepts with important security implications. Serverless shifts operational responsibility for servers to the provider but still requires secure permissions, data protection, dependency management, and event handling. Multicloud can reduce reliance on one provider but ma
Episode 50 — OT, Air-Gapped Networks, Microservices, and Segmentation
This episode covers operational technology, air-gapped networks, microservices, and segmentation as architecture choices that affect isolation, monitoring, and risk. Operational technology supports physical processes such as manufacturing, utilities, building systems, and industrial control, so availability and safety may be more important than rapid patching. Air-gapped networks are sepa
Episode 51 — Technical Architecture Tradeoffs: Availability, Resilience, Open Source, and Usability (3.1)
This episode explains how technical architecture decisions create tradeoffs across availability, resilience, responsibility, compute, power, recovery, and usability. For the Security+ exam, students should recognize that a design choice may improve one goal while creating cost, complexity, or operational risk somewhere else. High availability can reduce downtime but may require clustering
Episode 52 — Business Architecture Tradeoffs: Data Sovereignty, Classification, Cost, and Ownership (3.1)
This episode covers business architecture tradeoffs that influence secure design beyond purely technical preferences. Students should understand how data sovereignty affects where data may be stored, processed, or transferred, especially when laws or contracts require data to remain in certain jurisdictions. Classification drives handling, encryption, access, retention, and monitoring dec
Episode 53 — Scalability, Environmental Requirements, Risk, and Recovery Decisions (3.1)
This episode explains how scalability, environmental needs, risk, and recovery expectations influence secure architecture. Scalability means a system can grow to meet demand, but growth must be planned so security controls, logging, identity, network design, and data protection scale with it. Environmental requirements may include power, cooling, physical location, connectivity, hardware
Episode 54 — Infrastructure Protection: Device Placement, Security Zones, Attack Surface, and Diversity (3.2)
This episode introduces infrastructure protection by focusing on where controls are placed and how environments are divided. Students should understand that device placement affects visibility, enforcement, and risk, such as placing firewalls, sensors, proxies, and gateways where they can inspect the right traffic. Security zones separate systems by trust level, sensitivity, function, or
Episode 55 — Zero Trust Architecture: User, Device, and Application Decisions (3.2)
This episode explains Zero Trust architecture as a practical design approach where access decisions are based on identity, device health, application sensitivity, context, and risk. Students should understand that Zero Trust requires more than a strong login; it also depends on device inventory, posture checks, least privilege, segmentation, application access control, and continuous moni
Episode 56 — Secure Access: VPNs, Remote Access, Tunneling, and Encrypted Messaging (3.2)
This episode covers secure access technologies used to protect communication and allow users to reach systems from different locations. VPNs create encrypted connections over untrusted networks, while remote access tools support administration, support, and user productivity. Tunneling can carry one type of traffic through another protected channel, and end-to-end encrypted messaging prot
Episode 57 — Out-of-Band Management, File Transfer, and Security Service Edge (3.2)
This episode explains out-of-band management, secure file transfer, and Security Service Edge as architecture concepts tied to secure operations and access. Out-of-band management gives administrators a separate path to manage infrastructure when the primary network is unavailable, degraded, or compromised, but it must be strongly protected because it can provide powerful control. Secure
Episode 58 — Identity Architecture: gMSAs, Least Privilege Accounts, Privilege Creep, and Failure Modes (3.2)
This episode covers identity architecture as a core part of secure system design, especially where service accounts and administrative access are involved. Group managed service accounts help manage service credentials more safely by reducing manual password handling and supporting automatic credential management in appropriate environments. Least-privilege access accounts limit what user
Episode 59 — Data Types and States: Structured, Unstructured, At Rest, In Use, and In Transit (3.3)
This episode explains data types and data states, which are central to choosing the correct protection method. Structured data is organized in predictable formats such as databases and spreadsheets, while unstructured data includes documents, emails, images, chat records, and other content without a fixed schema. Data at rest is stored, data in transit is moving across a network, and data
Episode 60 — Data Classification: Public to Top Secret, Sensitive to Restricted (3.3)
This episode covers data classification labels and how they guide security decisions. Students should recognize common labels such as public, sensitive, confidential, restricted, critical, secret, and top secret, while understanding that exact labels vary by organization and industry. Classification helps determine who can access data, where it may be stored, whether it must be encrypted,
Episode 61 — Securing Data: Masking, Hashing, Filtering, Tokenization, Encryption, and Obfuscation (3.3)
This episode explains common methods used to protect data and how each method serves a different security purpose. Masking hides part of a value, such as showing only the last digits of an account number, while hashing creates a fixed integrity value that should not be reversible. Filtering removes or blocks data based on rules, tokenization replaces sensitive values with substitute token
Episode 62 — Data Protection Roles: Owner, Custodian, Steward, Operator, Controller, and Subprocessor (3.3)
This episode covers data protection roles and explains how responsibility is divided across people and organizations. A data owner is accountable for decisions about data use and protection, while a custodian manages storage, systems, and technical safeguards. A steward helps maintain quality, classification, and proper handling, and an operator may process or manage data according to ass
Episode 63 — Data Handling, Geofencing, Lifecycle, Retention, Disposal, and Compliance (3.3)
This episode explains data handling across the full data lifecycle, from creation and collection through storage, use, sharing, retention, archival, and disposal. Students should understand that data protection is not limited to encryption; it also includes classification, approved storage locations, access rules, handling procedures, transfer methods, and disposal requirements. Geofencin
Episode 64 — Resilience Sites: Hot, Warm, Cold, and Environmental Planning (3.4)
This episode explains hot, warm, and cold recovery sites and how they support resilience and disaster recovery planning. A hot site is ready for rapid failover with systems, connectivity, and data prepared for use, while a warm site has some infrastructure ready but may require configuration or data restoration. A cold site provides space and basic facilities but requires more setup befor
Episode 65 — Platform Diversity, Load Balancing, Clustering, Autoscaling, and High Availability (3.4)
This episode covers design methods that improve resilience and reduce single points of failure. Platform diversity can reduce the chance that one common flaw affects every system, though it may increase management complexity. Load balancing distributes traffic across multiple systems to improve performance and availability, while clustering allows systems to work together so one node can
Episode 66 — Power, Storage, Backups, Immutability, and Restoration Testing (3.4)
This episode explains resilience controls related to power, storage, backups, immutability, and recovery validation. Uninterruptible power supplies provide short-term power during interruptions, redundant power supplies reduce hardware failure risk, generators support longer outages, and surge protection helps protect equipment from electrical damage. Storage resilience may involve redund
Episode 67 — Disaster Recovery and Business Continuity: Failover, Simulation, Parallel Processing, and Capacity Planning (3.4)
This episode explains the relationship between disaster recovery and business continuity. Disaster recovery focuses on restoring technology and data after disruption, while business continuity focuses on keeping essential business functions operating during and after an incident. Students should understand failover testing, simulations, tabletop exercises, parallel processing, and capacit
Episode 68 — Recovery Metrics: RTO, RPO, MTTR, and MTBF (3.4)
This episode explains four recovery and reliability metrics that frequently appear in Security+ questions. Recovery time objective defines the maximum acceptable time to restore a service after disruption, while recovery point objective defines the maximum acceptable amount of data loss measured in time. Mean time to repair measures the average time needed to restore a failed component or
Episode 69 — Mitigating Controls Overview: Segmentation, Access Control, Hardening, and Sandboxing (4.1)
This episode introduces mitigating controls as practical actions that reduce risk after threats, vulnerabilities, or exposures are identified. Segmentation limits movement between systems or zones, access control restricts who or what can reach resources, hardening removes unnecessary services and insecure settings, and patching addresses known weaknesses. Isolation and sandboxing contain
Episode 70 — Deception and Disruption: Honeypots, Honeynets, Honeyfiles, Honeytokens, and Canary Accounts (4.1)
This episode explains deception technologies that help detect, study, or slow attackers by presenting attractive fake targets or monitored artifacts. A honeypot is a decoy system, while a honeynet is a collection of decoy systems designed to observe attacker behavior. Honeyfiles are fake files placed where unauthorized access would be suspicious, honeytokens are monitored values such as f
Episode 71 — Monitoring, MDM, Allow Lists, Block Lists, IDS, IPS, and WIPS (4.1)
This episode covers monitoring and access control technologies that help organizations identify suspicious behavior and reduce exposure. Monitoring provides visibility into systems, users, devices, and network activity, while mobile device management helps enforce configuration, encryption, application, and remote wipe policies on phones, tablets, and other managed endpoints. Allow lists
Episode 72 — Firewalls and Filtering: WAF, UTM, Layer 4/Layer 7, Rate Limiting, and DLP (4.1)
This episode compares firewall and filtering technologies by focusing on what each control is designed to inspect, block, or allow. Traditional firewalls often filter traffic by addresses, ports, and protocols, while Layer 4 controls focus on transport-level details and Layer 7 controls inspect application-level content. A web application firewall protects web applications from attacks su
Episode 73 — Endpoint and Network Access Control: EDR, XDR, Antivirus, Captive Portals, 802.1X, and Posture (4.1)
This episode explains how endpoint protection and network access control help determine whether a device should be trusted, monitored, restricted, or blocked. Antivirus focuses on known malicious files and behavior, while endpoint detection and response provides deeper investigation, containment, and response capabilities on endpoints. Extended detection and response correlates signals ac
Episode 74 — Repository, Application, and Code Security: Secrets Scanning, Input Validation, Secure Cookies, Static Analysis, and Code Signing (4.1)
This episode covers security controls that protect code, applications, and software repositories from preventable weaknesses. Secrets scanning detects exposed API keys, passwords, tokens, certificates, or credentials before they are misused. Input validation checks that submitted data follows expected rules before an application processes it, reducing the risk of injection and malformed r
Episode 75 — Email and OS Security: DMARC, SPF, DKIM, BIMI, Group Policy, and SELinux (4.1)
This episode explains email authentication and operating system security controls that help enforce trust and configuration standards. Sender Policy Framework helps identify which mail servers are authorized to send mail for a domain, DomainKeys Identified Mail uses cryptographic signatures to validate message integrity and domain association, and Domain-based Message Authentication, Repo
Episode 76 — Asset Management: Hardware, Software, and Data Life Cycle (4.2)
This episode introduces asset management as a security foundation for hardware, software, and data throughout their life cycles. Students should understand that organizations cannot reliably patch, monitor, classify, protect, or retire assets they do not know exist. Hardware inventories identify devices such as laptops, servers, mobile devices, network equipment, and removable media. Soft
Episode 77 — Planning, Procurement, Assignment, Tracking, Disposal, and Decommissioning (4.2)
This episode covers the asset lifecycle from planning and procurement through assignment, accounting, tracking, disposal, and decommissioning. Planning defines what the organization needs and what security requirements must be built in before purchase. Procurement should consider approved vendors, licensing, supportability, compliance, and secure configuration requirements. Assignment and
Episode 78 — Vulnerability Management Overview: Scanning, IPAM, CSPM, and Source Code Review (4.3)
This episode explains vulnerability management as a recurring operational process rather than a one-time scan. Vulnerability scanning identifies known weaknesses in systems, applications, configurations, and network exposure, but findings must be validated, prioritized, remediated, and verified. IP address management helps teams understand what systems exist, where they are located, and w
Episode 79 — Prioritization: Severity, Business Impact, and Pen Test Report Review (4.3)
This episode teaches students how to prioritize vulnerabilities and penetration test findings using more than severity alone. Severity helps describe technical risk, but remediation priority also depends on exploitability, exposure, asset criticality, business impact, compensating controls, data sensitivity, and whether the weakness is actively being exploited. A public-facing system that
Episode 80 — Remediation, Verification, and Internal Reporting (4.3)
This episode explains what happens after a vulnerability or weakness has been identified and prioritized. Remediation may involve patching, configuration changes, disabling exposed services, rotating credentials, improving access control, deploying compensating controls, or accepting risk through an approved process when immediate correction is not practical. Verification confirms whether
Recommended
Booked, Blonde & Busy w/ Olivia Ponton
The Human-Animal Connection - Pet Life Radio Original
Medicine with Meaning
Homemaking with Jesus | Weekly Devotionals, Biblical Application, Simple Living, Home Management, Healthy Relationships
Disney+ Hulu Throwbacks Podcast
The Daily
World News Tonight with David Muir
English Vocabulary Help
The Joe Rogan Experience
TED Talks Daily
SLOW ENGLISH PODCAST (A1-A2) With Subtitles | Daily Videos | English With Us Podcast
Stand In The Circle
