<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:podcast="https://podcastindex.org/namespace/1.0"><channel><title>Cybersecurity Research Podcast</title><link>https://apimade.com/podcasts/research/</link><description>Practical audio explanations of new cybersecurity research.</description><language>en-au</language><atom:link href="https://apimade.com/podcasts/research/podcast.xml" rel="self" type="application/rss+xml"/><item><guid isPermaLink="false">acdfb5bc-888e-46bc-bf1f-d8ff9371f016</guid><title>MORPHEUS: A Multidimensional Framework for Modeling, Measuring, and Mitigating Human Factors in Cybersecurity</title><link>https://apimade.com/podcasts/research/morpheus-a-multidimensional-framework-for-modeling-measuring-and-m-7e2eae94/</link><pubDate>Mon, 31 Aug 2026 12:02:34 +0000</pubDate><description>Researchers combined a systematic scoping review with AI-assisted, human-validated screening to organize human factors, their interactions, and measurement instruments in cybersecurity. MORPHEUS can support risk diagnosis and targeted interventions. Separately, cited studies associate missing information, time, tools, and training with incorrect or delayed configuration correction, while absent periodic audits, continuous monitoring, and education may leave cloud misconfigurations unresolved.
A technical explanation of the paper's research question, method, reported findings and limitations. The resulting framework organizes 50 human factors across 6 dimensions. Factors closer to a security decision sit in the cognition, affect, and behavior core; affect here means emotional state. More distant influences include personality, demographics, and…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/7426367e-ff49-4985-bbd9-b9daf5f2c345/13986fb6-61b6-4cdd-8999-0c9ce4922cb9.mp3" length="5213612" type="audio/mpeg"/><itunes:duration>326</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/morpheus-a-multidimensional-framework-for-modeling-measuring-and-m-7e2eae94/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">5c315bf0-1514-46fe-8445-55b5b5d20e33</guid><title>Out of Sight, Not Out of Mind: Unveiling Latent Attack in Latent-based Multi-Agent Systems</title><link>https://apimade.com/podcasts/research/out-of-sight-not-out-of-mind-unveiling-latent-attack-in-latent-bas-5b3e6e8e/</link><pubDate>Mon, 31 Aug 2026 07:27:32 +0000</pubDate><description>Researchers constructed attack-associated steering vectors from paired clean and attacked runs, injected them into agents’ hidden states and KV-cache handoffs without adversarial text, and observed substantial task-performance degradation, especially through inter-agent handoffs. Security teams should therefore monitor and restrict latent-state infrastructure rather than rely on visible-message inspection, although the evaluated attacker required privileged access to intermediate states and the experiments did not exhaust the intervention space.
A technical explanation of the paper's research question, method, reported findings and limitations. Optimization-based extraction produced more effective attacks than training-free geometric methods in the evaluated settings. On attack location, latent-based systems were more vulnerable at communication handoffs than at local agent states. Attack-derived…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5204223f-0c7c-4456-85b1-1c02edb87460/18d2f255-808e-4ad3-881d-b52d6eecce8b.mp3" length="5371052" type="audio/mpeg"/><itunes:duration>336</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/out-of-sight-not-out-of-mind-unveiling-latent-attack-in-latent-bas-5b3e6e8e/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">a7e1015c-7d80-47ba-9ba2-effa254fcf8a</guid><title>Cybersecurity Budgeting: A Cyber Risk Perspective</title><link>https://apimade.com/podcasts/research/cybersecurity-budgeting-a-cyber-risk-perspective-f3d5f9a1/</link><pubDate>Mon, 31 Aug 2026 07:01:15 +0000</pubDate><description>The paper develops an economic framework for preventive cybersecurity budgeting based on the Gordon–Loeb model, cataloguing budgeting challenges, arguing for an initial spending upper bound, and proposing ways to align spending authority with accountability. Security leaders can use it to structure risk-based investment and governance discussions, but the study did not empirically test its arguments.
A technical explanation of the paper's research question, method, reported findings and limitations. Within the model, optimal preventive investment has an upper bound based on expected loss. This is not a universal spending target. The analysis also starts from the premise that 100% cybersecurity is infeasible and that overspending can waste scarce…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5b1939ef-4e36-4ab8-a9c5-5f6e3c06b132/a2eaf97a-8016-4586-8d97-ed5b49e4a934.mp3" length="5154860" type="audio/mpeg"/><itunes:duration>322</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/cybersecurity-budgeting-a-cyber-risk-perspective-f3d5f9a1/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">d17ca68a-b432-4f61-a5e4-a57839de223f</guid><title>eBPF-based cybersecurity mechanisms: a systematic literature review</title><link>https://apimade.com/podcasts/research/ebpf-based-cybersecurity-mechanisms-a-systematic-literature-review-1279f515/</link><pubDate>Mon, 31 Aug 2026 07:00:29 +0000</pubDate><description>The review synthesized peer-reviewed research and found that evaluated eBPF mechanisms often combined low-overhead enforcement with strong detection performance, especially for kernel monitoring, real-time packet processing, and cloud-native workload protection. For deployment, treat those results as promising but context-bound: kernel fragmentation hinders portability, most work leaves eBPF’s own vulnerabilities unaddressed, and shared-kernel container designs cannot provide complete isolation.
A technical explanation of the paper's research question, method, reported findings and limitations. The synthesis found eBPF being used as both a sensor and an enforcement point. Systems collected kernel events and system-call traces. They also gathered network-flow data. Those inputs supported detection, observability, and policy enforcement. The reviewed…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/3157240a-d849-421d-b63f-565572bc765a/1214e9bc-3680-494b-afa8-79982b66c0b0.mp3" length="5244332" type="audio/mpeg"/><itunes:duration>328</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/ebpf-based-cybersecurity-mechanisms-a-systematic-literature-review-1279f515/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">9ca9a609-1179-475b-9065-c5daf7186473</guid><title>Research on Edge-Cloud Collaborative Resource Scheduling and Security Management Based on Intelligent Optimization and Privacy Protection</title><link>https://apimade.com/podcasts/research/research-on-edge-cloud-collaborative-resource-scheduling-and-secur-d8466669/</link><pubDate>Mon, 31 Aug 2026 06:59:51 +0000</pubDate><description>Tianyu Luo reviewed edge-cloud scheduling and privacy research, then proposed a decision model that weighs performance, cost, node trust, data sensitivity, privacy risk, reliability and auditability. For security architects and edge-platform teams, it offers a design checklist for making trust and privacy part of task placement, but the article does not test the idea experimentally, so operational benefits remain untested.
A technical explanation of the paper's research question, method, reported findings and limitations. The analysis identifies a continuing separation between intelligent resource scheduling and privacy-aware security management. Luo responds with a weighted decision model. It weighs latency, energy and cost against privacy risk and node trust. Reliability is…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/4abfd1a0-7f47-42fd-aa5a-a802b5b7cf3d/0e205926-eab7-4eb1-bec7-51de6dc466f5.mp3" length="5631020" type="audio/mpeg"/><itunes:duration>352</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/research-on-edge-cloud-collaborative-resource-scheduling-and-secur-d8466669/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">b4e9630d-4e2a-40f6-86cd-6f0ba1d3ee96</guid><title>AGENTSHIELD: AN AGENTIC ARTIFICIAL INTELLIGENCE FRAMEWORK FOR REAL-TIME CYBERSECURITY ORCHESTRATION IN INDIA’S UPI AND FINTECH ECOSYSTEM</title><link>https://apimade.com/podcasts/research/agentshield-an-agentic-artificial-intelligence-framework-for-real-a836f684/</link><pubDate>Mon, 31 Aug 2026 06:47:44 +0000</pubDate><description>The researchers propose Agent Shield, a real-time cybersecurity orchestration framework with coordinated threat-intelligence, transaction-anomaly, behavioral-biometric, and compliance agents. In a comparative evaluation, it achieved 98.7% fraud-detection accuracy and lower detection time and false-positive rates than existing approaches. A stated limitation of ML-only approaches is dependence on labelled training data when novel attacks have no prior labels.
A technical explanation of the paper's research question, method, reported findings and limitations. The comparative evaluation covers mandated controls and an existing fraud-detection stack. It also covers machine-learning-only pipelines, security monitoring and zero-trust architecture. The reported results pair high fraud-detection accuracy with large…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/2748c622-7397-4926-a5be-c39e18ae4f9e/7f47129f-35bd-4738-8e09-d7906b5108a2.mp3" length="5740844" type="audio/mpeg"/><itunes:duration>359</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/agentshield-an-agentic-artificial-intelligence-framework-for-real-a836f684/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">62edcdbb-6afe-4893-912c-81781594abed</guid><title>Secure Cloud-Native Platforms for Critical Service Continuity: An AI-Driven Framework for National Cyber and Economic Resilience</title><link>https://apimade.com/podcasts/research/secure-cloud-native-platforms-for-critical-service-continuity-an-a-fc7ad308/</link><pubDate>Mon, 31 Aug 2026 06:47:05 +0000</pubDate><description>Researchers designed AICER as a conceptual decision-support architecture linking cloud-native operations, cyber intelligence, AI-assisted analytics, secure delivery, supply-chain assurance, economic impact assessment, and governance, using an integrative literature and standards review. For security teams, it offers a structure for coordinating continuity controls while keeping AI suggestions under human oversight, but its benefits remain unvalidated because the work provides no numerical simulation or synthetic experimental evidence.
A technical explanation of the paper's research question, method, reported findings and limitations. The resulting architecture organizes its layers into a staged decision path. The architecture includes critical-service objectives and recovery priorities. It also includes cloud workload and service-health data. An intelligence stage combines operational…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/7e1d84fe-7abc-43ad-b86d-cc03c3771460/429fa2d3-7949-4db6-a87e-409bcfa8062f.mp3" length="6579500" type="audio/mpeg"/><itunes:duration>411</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/secure-cloud-native-platforms-for-critical-service-continuity-an-a-fc7ad308/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">db67e292-fbb7-491e-9e4e-565f9599f7fe</guid><title>DIGITAL MATURITY: EVIDENCE FROM A 24-COMPANY ASSESSMENT WITH THE RR-FRAMEWORK</title><link>https://apimade.com/podcasts/research/digital-maturity-evidence-from-a-24-company-assessment-with-the-rr-08483464/</link><pubDate>Mon, 31 Aug 2026 06:41:38 +0000</pubDate><description>The study combined a broad resilience assessment with confidence adjustments, crisis stress tests and tail-risk modeling. Lower maturity was associated with greater modeled loss, while red-line breaches were reported descriptively. In the evaluated setting, security teams may use the results to prioritize cyber/privacy and IT-continuity weaknesses within wider resilience planning. The evidence derives from a deliberately heterogeneous portfolio of synthetic organizations used as a calibration sample.
A technical explanation of the paper's research question, method, reported findings and limitations. Average maturity across the portfolio was 2.59 out of 5, with substantial variation among organizations. Higher maturity was associated with fewer cases where controls crossed critical limits. It was also associated with smaller shortfalls from target and…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/2d494868-d21f-431d-8869-0562b7afb96a/17795396-fa72-4a32-9622-2e1f635699ba.mp3" length="4395308" type="audio/mpeg"/><itunes:duration>275</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/digital-maturity-evidence-from-a-24-company-assessment-with-the-rr-08483464/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">dcfbe506-9b32-48b2-ac73-983526996650</guid><title>Reciprocal Disclosure and the Ethics of Vulnerability Reporting: A Cybersecurity Ethics Case Study of Nightmare Eclipse</title><link>https://apimade.com/podcasts/research/reciprocal-disclosure-and-the-ethics-of-vulnerability-reporting-a-ba28a9a6/</link><pubDate>Mon, 31 Aug 2026 03:55:30 +0000</pubDate><description>Herrick analyzes Nightmare Eclipse, where a researcher moved from cooperative reporting to publishing Windows zero-days after alleging dismissal, undervaluation and legal intimidation; 3 of the first 6 disclosed flaws were exploited in the wild and chained with ransomware. Security teams should keep reporting channels functional and distinguish vulnerability intake from bounty incentives, while recognizing that nondisclosure terms can sometimes bind researchers even when a report is rejected and never fixed.
A technical explanation of the paper's research question, method, reported findings and limitations. Between April and June 2026, the researcher publicly released at least 8 Windows zero-day exploits, including vulnerabilities affecting Defender. Of these disclosures, 3 were exploited in the wild and chained with ransomware. Microsoft eventually patched…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/3017ff8a-1b87-48a3-a4a3-eb909f807854/71f2e0cb-3b1a-490e-8f14-a0636b59c9cf.mp3" length="4947500" type="audio/mpeg"/><itunes:duration>309</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/reciprocal-disclosure-and-the-ethics-of-vulnerability-reporting-a-ba28a9a6/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">a5c1e4f9-3d77-44db-bf72-fe85a5ecd3f7</guid><title>Security and Privacy Implications of Microsoft 365 Copilot and GenAI Integration in Enterprise Environments</title><link>https://apimade.com/podcasts/research/security-and-privacy-implications-of-microsoft-365-copilot-and-gen-4a06218d/</link><pubDate>Mon, 31 Aug 2026 03:54:53 +0000</pubDate><description>Using a secondary qualitative review and STRIDE threat modeling, the authors mapped how Copilot’s access to email, files, chats, and calendars can expose enterprises to prompt injection, model interference, unauthorized access, and information leakage. Security teams should pair technical controls with organizational and regulatory governance, but treat the recommendations as threat-model guidance rather than measured risk: the study relies on public documentation and lacks primary empirical data.
A technical explanation of the paper's research question, method, reported findings and limitations. The analysis linked exposure to Copilot's broad access and its ability to operate across several productivity applications. That combination can widen the attack surface when permissions or boundaries are too broad. Microsoft Purview was one baseline…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/4cc732e4-3fe0-4636-a622-d5e2aecb8020/07e62eed-296f-4dfb-93d8-b50451e04840.mp3" length="6951980" type="audio/mpeg"/><itunes:duration>434</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/security-and-privacy-implications-of-microsoft-365-copilot-and-gen-4a06218d/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">4e9b9055-1978-4074-9ab7-7f19733ffe12</guid><title>AI-Driven Threat Detection and Automated Incident Response for Securing Cloud Workloads</title><link>https://apimade.com/podcasts/research/ai-driven-threat-detection-and-automated-incident-response-for-sec-0660a2b8/</link><pubDate>Mon, 31 Aug 2026 03:54:09 +0000</pubDate><description>Researchers compared an AI-augmented cloud security architecture integrating SIEM, XDR, behavioral analytics, AI-assisted correlation and SOAR with manual triage and signature-based controls across phishing-led account takeover, multi-stage ransomware and shadow-IT exfiltration scenarios. For SOCs, the study supports evaluating integrated automation for cloud response, but its 30-day window and selected scenarios limit generalisation; ambiguous social-engineering and encrypted-content cases still require analyst judgment.
A technical explanation of the paper's research question, method, reported findings and limitations. Mean triage took 17.4 hours in the conventional baseline and 10.7 minutes in the AI-augmented environment. Preconfigured automated playbooks also contained ransomware within minutes. The researchers observed better prioritization of high-severity incidents,…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/eac8872e-0799-4aad-b785-1e83f3e173e2/ee5f742f-b006-4203-a8ab-97b093657327.mp3" length="6085292" type="audio/mpeg"/><itunes:duration>380</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/ai-driven-threat-detection-and-automated-incident-response-for-sec-0660a2b8/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">07cacf13-52cf-4c59-9763-f8c76a95cae6</guid><title>Enterprise Infrastructure Modernization Framework for Hybrid Cloud Transformation: A Governed Workload-Centered Approach</title><link>https://apimade.com/podcasts/research/enterprise-infrastructure-modernization-framework-for-hybrid-cloud-60903410/</link><pubDate>Mon, 31 Aug 2026 03:53:27 +0000</pubDate><description>Gopalakrishnan organizes hybrid-cloud modernization around workload assessment, strategy selection, target architecture, platform engineering, and continuing governance, with readiness checks linking design, build, migration, operations, and optimization. Security and platform teams can use those checks to keep controls and monitoring from becoming post-migration cleanup, but the evidence comes from specific enterprise programs rather than a randomized study and may not transfer uniformly elsewhere.
A technical explanation of the paper's research question, method, reported findings and limitations. At the workload level, EIMF examines 9 considerations through a few practical questions. What is the workload’s technical condition and support status? What are its performance needs and data sensitivity? What does recovery require, and which dependencies…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/2e399213-f92b-46d5-83ec-7a4b1f407b0f/88096d81-f190-4994-8599-f93b80b9a777.mp3" length="5502764" type="audio/mpeg"/><itunes:duration>344</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/enterprise-infrastructure-modernization-framework-for-hybrid-cloud-60903410/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">6671f63d-e088-4c56-864f-65831fd41441</guid><title>Enterprise Integration Modernization with SAP BTP</title><link>https://apimade.com/podcasts/research/enterprise-integration-modernization-with-sap-btp-77c10165/</link><pubDate>Mon, 31 Aug 2026 03:52:42 +0000</pubDate><description>Using a synthetic enterprise landscape, Puppala compared legacy point-to-point integration with an SAP BTP-centered architecture and measured lower latency, recovery time and failed-message rates. Security and integration teams can use the framework to prioritize fragile, business-critical interfaces and embed access control, audit and runtime visibility, but the synthetic data cannot establish that the gains will carry into every real enterprise.
A technical explanation of the paper's research question, method, reported findings and limitations. In the synthetic comparison, average integration latency moved from 420 milliseconds in the legacy baseline to 245 milliseconds in the BTP-centered design. This is a measurement inside the modelled landscape, not evidence that installing BTP by itself will…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/a1aa320a-026c-46e5-9742-6b9120363aa4/3a501b9a-43a3-4997-a6b6-68365d2a7710.mp3" length="6261164" type="audio/mpeg"/><itunes:duration>391</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/enterprise-integration-modernization-with-sap-btp-77c10165/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">eceeb977-b099-4ed6-a334-fb8fcfaeb188</guid><title>Cryptocurrency as a Payment Method for Ransomware Cybercrime Lockbit Ransomware and the Implementation of Cyberlaw and Cybersecurity</title><link>https://apimade.com/podcasts/research/cryptocurrency-as-a-payment-method-for-ransomware-cybercrime-lockb-f9a692b3/</link><pubDate>Mon, 31 Aug 2026 03:52:05 +0000</pubDate><description>Using a normative legal analysis of Indonesian criminal, electronic-information and personal-data law, the paper argues that cryptocurrency enables LockBit ransom payments, while leaked wallet addresses and blockchain forensics can support tracing and possible wallet freezes. Enforcement remains difficult because attackers use TOR/VPN and international perpetrators present jurisdictional difficulties, while Indonesian regulations are not yet specific to cryptocurrency ransom and do not fully capture double extortion.
A technical explanation of the paper's research question, method, reported findings and limitations. The analysis treats cryptocurrency in Indonesia as a regulated crypto-asset commodity rather than legal tender. On that basis, LockBit transactions do not qualify as legal payments, although they may remain valid as commodity exchanges carrying civil risks.…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/9436c681-3a04-4189-9d16-2c61474247bd/a80d89f7-028d-437b-9d2e-49aab391cf6c.mp3" length="4164140" type="audio/mpeg"/><itunes:duration>260</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/cryptocurrency-as-a-payment-method-for-ransomware-cybercrime-lockb-f9a692b3/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">56a169f6-3223-4737-84ff-51add6eff8a1</guid><title>A Control-Driven Framework for Secure SaaS Onboarding in Regulated Enterprises</title><link>https://apimade.com/podcasts/research/a-control-driven-framework-for-secure-saas-onboarding-in-regulated-443546dd/</link><pubDate>Mon, 31 Aug 2026 03:51:19 +0000</pubDate><description>Thota and Dulam propose a control-driven SaaS onboarding lifecycle integrating vendor risk, cybersecurity, identity, and DR, while distinguishing vendor-level assurance from validation of enterprise-specific tenant configurations. The framework maps control activities to responsible owners and evidence artifacts. Recovery objectives depend on vendor contractual commitments, and vendor attestations cannot substitute for platform-specific tabletop exercises.
A technical explanation of the paper's research question, method, reported findings and limitations. The resulting framework makes vendor assurance and tenant validation separate control decisions. Pre-contract review determines whether the provider meets the enterprise's risk threshold. Post-contract review tests the actual tenant configuration. Production…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/092a11f6-e76c-45a0-b1d1-49642a71e538/c73b32d0-9d80-439c-9eb1-978348d44d50.mp3" length="5308460" type="audio/mpeg"/><itunes:duration>332</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/a-control-driven-framework-for-secure-saas-onboarding-in-regulated-443546dd/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">1e9394d6-c469-4881-bca2-321232978bb3</guid><title>The Influence of Cybersecurity Practices on Project Management in Software Engineering</title><link>https://apimade.com/podcasts/research/the-influence-of-cybersecurity-practices-on-project-management-in-0c6a3a19/</link><pubDate>Mon, 31 Aug 2026 03:47:33 +0000</pubDate><description>In a survey of 128 software engineering experts, stronger risk management preparedness was associated with more favorable perceptions of timeline management, budgeting and team collaboration. Respondents also identified training, budget constraints, unclear roles, late cybersecurity integration and limited collaboration as challenges. The findings suggest ongoing training, budget planning, role definition and earlier cybersecurity inclusion, but self-reported, purposively sampled perceptions may be biased and may not generalize.
A technical explanation of the paper's research question, method, reported findings and limitations. Respondents commonly perceived that integrating security increased project costs, although opinions varied. Several also thought security could delay timelines, but they did not generally view those delays as a large disruption across all projects.…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/82a2943f-ecb2-46c5-8dbe-6ffc5481dd4b/458373ee-8c91-4864-982c-f9b576b89b87.mp3" length="5753900" type="audio/mpeg"/><itunes:duration>360</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-influence-of-cybersecurity-practices-on-project-management-in-0c6a3a19/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">5b7743c6-0e0a-4d3c-8c1a-a54cb43cde31</guid><title>SECURING HEALTHCARE INFORMATION SYSTEMS AGAINST RANSOMWARE: A RISK-BASED FRAMEWORK</title><link>https://apimade.com/podcasts/research/securing-healthcare-information-systems-against-ransomware-a-risk-fbe91479/</link><pubDate>Mon, 31 Aug 2026 03:46:46 +0000</pubDate><description>Ali proposed a healthcare ransomware framework that assesses threats based on asset criticality, vulnerability severity, likelihood of exploitation and potential operational impact, then includes preventive, detective, response and recovery controls. It can help organisations allocate scarce cybersecurity resources to protect critical services and patient safety, but incomplete incident data and variation among hospitals mean conclusions from selected cases and representative settings may not apply everywhere.
A technical explanation of the paper's research question, method, reported findings and limitations. The assessment places systems that control identity, deliver care and support administration among the most vulnerable, along with connected medical devices and backup infrastructure. Exposure is highest where authentication and privileges are weak, networks…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/9aa9d488-e28f-452d-b80d-99e01bb079d7/e6f0e28f-1a89-49cb-9474-f3c6ac6e8613.mp3" length="6546092" type="audio/mpeg"/><itunes:duration>409</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/securing-healthcare-information-systems-against-ransomware-a-risk-fbe91479/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">78f24bf5-4f2e-4b89-822d-9d2200f2eab7</guid><title>Workplace Surveillance and Insider Threat Risk Management: Legal Limits and Privacy Harms</title><link>https://apimade.com/podcasts/research/workplace-surveillance-and-insider-threat-risk-management-legal-li-7625dc87/</link><pubDate>Thu, 27 Aug 2026 21:31:26 +0000</pubDate><description>Through a literature review of workplace surveillance tools, practices, laws and privacy harms, the researchers identified gaps in monitoring transparency, insider-threat education and the use of behavioral indicators in detection systems. Security teams can use its recommendations to focus monitoring on work-related signals and reduce log noise, but the paper warns that excessive logging creates operator alert fatigue and uniform federal rules may overlook regional privacy differences.
A technical explanation of the paper's research question, method, reported findings and limitations. The analysis groups insider risk into accidental actions, deliberate actions, and actions driven by an available opportunity. It argues that the prospect of insider threats within an organization should be the target of employee surveillance. The review also…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/3a8ce7ba-5d45-4b4f-9300-f59e997f5a49/27d2d690-72f2-4438-aa3c-331db163d0e8.mp3" length="4528940" type="audio/mpeg"/><itunes:duration>283</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/workplace-surveillance-and-insider-threat-risk-management-legal-li-7625dc87/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">aca3869d-ec8f-478c-9cdc-79c299a14615</guid><title>AgentDojo: A Dynamic Environment to Evaluate Prompt Injection Attacks and Defenses for LLM Agents</title><link>https://apimade.com/podcasts/research/agentdojo-a-dynamic-environment-to-evaluate-prompt-injection-attac-f9cd22d5/</link><pubDate>Tue, 25 Aug 2026 04:16:54 +0000</pubDate><description>AgentDojo turns prompt-injection evaluation into an executable, stateful test: tool-using agents must complete legitimate tasks while deterministic checks detect adversarial effects. Security teams can use it to compare tested defenses, but its dataset is synthetic and static, users assigning multiple tasks over time without context reset are not covered, and comparisons must be pinned to exact versions because an implementation bug was fixed and Travel was updated.
A technical explanation of the paper's research question, method, reported findings and limitations. Across the evaluated model configurations, greater task capability tended to come with greater success at executing attacker goals. Most models also lost 10 to 25 percentage points of task utility when attacked. This was not a simple winner-takes-all ranking.…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/a46cb8e3-133c-4e9d-91f9-437ff03b7694/10394e6f-e7af-4e25-8b7a-87b89359e9d6.mp3" length="4895660" type="audio/mpeg"/><itunes:duration>306</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/agentdojo-a-dynamic-environment-to-evaluate-prompt-injection-attac-f9cd22d5/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">9951e314-59d4-4ded-92db-6c415118c935</guid><title>Universal and Transferable Adversarial Attacks on Aligned Language Models</title><link>https://apimade.com/podcasts/research/universal-and-transferable-adversarial-attacks-on-aligned-language-370efadf/</link><pubDate>Tue, 25 Aug 2026 04:16:07 +0000</pubDate><description>Zou and colleagues automated jailbreak discovery by optimizing reusable adversarial suffixes on source models, then measured transfer to held-out harmful requests and several other models, with success varying sharply by target. Security teams can use this pattern for repeatable evaluations, but the tests covered prohibited text generation at a 2023 snapshot—not consequential agent compromise or durability across model and API updates.
A technical explanation of the paper's research question, method, reported findings and limitations. The evaluation used AdvBench collections constructed from hand-written seeds and outputs from an uncensored model. In white-box testing, GCG succeeded on nearly all harmful-behavior tests for Vicuna-7B, compared with just over half for LLaMA-2-7B-Chat. That…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/6583bfe0-9b10-4561-983d-65df8f12fb73/aee905ea-450f-4c06-81e4-4db696f19572.mp3" length="4678700" type="audio/mpeg"/><itunes:duration>292</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/universal-and-transferable-adversarial-attacks-on-aligned-language-370efadf/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">aff0bd62-1c39-46de-ac9b-e8673c1b748f</guid><title>Not What You've Signed Up For: Compromising Real-World LLM-Integrated Applications with Indirect Prompt Injection</title><link>https://apimade.com/podcasts/research/not-what-youve-signed-up-for-compromising-real-world-llm-integrate-73a9eddf/</link><pubDate>Tue, 25 Aug 2026 04:15:26 +0000</pubDate><description>Across controlled LLM applications and Bing Chat, Greshake and colleagues showed that adversarial instructions in retrieved content could steer responses, trigger tool-mediated data leakage, spread through synthetic email, and persist through memory. Security teams should treat retrieved data as a possible control input, while recognizing that the study did not estimate attack success rates or test public poisoning.
A technical explanation of the paper's research question, method, reported findings and limitations. The demonstrations established that indirectly supplied instructions could steer model behavior, bypass some filtering applied to direct chat, and sometimes remain influential later in a conversation. In information-gathering examples, the model generated a…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5690f332-5a58-40d3-ae79-1087ec088e72/b6d09c63-3b4a-47c8-a3fd-014a9298538c.mp3" length="6233900" type="audio/mpeg"/><itunes:duration>390</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/not-what-youve-signed-up-for-compromising-real-world-llm-integrate-73a9eddf/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">5b2b02cd-06c3-456c-ac04-4a9d385a8bb7</guid><title>Sigstore: Software Signing for Everybody</title><link>https://apimade.com/podcasts/research/sigstore-software-signing-for-everybody-3b42a262/</link><pubDate>Tue, 25 Aug 2026 04:14:44 +0000</pubDate><description>Newman, Meyers, and Torres-Arias combined identity-based short-lived certificates, transparency logs, trust-root distribution, and usable clients into Sigstore, while measurements found online verification took roughly 1.5 seconds in their setup. Release and identity teams can reduce persistent-key handling, but they still need authorization policy, monitoring, and recovery plans because a valid signature does not prove safe code or stop a compromised account.
A technical explanation of the paper's research question, method, reported findings and limitations. For operational evidence, the authors conducted 7 guided interviews that followed a prepared structure while allowing follow-up questions. Participants had experience with Kubernetes, RubyGems, a Java client, or open-source use. The authors also repeated…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/827efcee-425e-4f42-86bc-9734d4f935e8/ce213c13-be17-40a5-b643-8c84ea564740.mp3" length="5624492" type="audio/mpeg"/><itunes:duration>351</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/sigstore-software-signing-for-everybody-3b42a262/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">a90dfde4-1c9e-4fa7-94af-e809a76a3a6c</guid><title>The Ballot is Busted Before the Blockchain: A Security Analysis of Voatz, the First Internet Voting Application Used in U.S. Federal Elections</title><link>https://apimade.com/podcasts/research/the-ballot-is-busted-before-the-blockchain-a-security-analysis-of-ac242526/</link><pubDate>Tue, 25 Aug 2026 04:14:03 +0000</pubDate><description>The researchers tested Voatz’s Android client against a researcher-built server and found that device, network-path, identity-service, and API-server adversaries could variously suppress or alter ballots, learn secret votes, or expose identity and IP information. A malicious API server could act before blockchain processing. They urged publication of source, design, threat models, and operational details while noting they did not test production backend, iOS client, blockchain, audit portal, or live configuration.
A technical explanation of the paper's research question, method, reported findings and limitations. On a rooted Android device, an attacker could disable the Zimperium defensive component by overriding its software entry points. The attacker could then read authentication data and vote history. The same access could alter a ballot while continuing to…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/54b47f7f-424b-411c-b8f5-d0fea1b47104/da8d8521-0b6f-41aa-925a-35c74b75ded1.mp3" length="4681004" type="audio/mpeg"/><itunes:duration>293</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-ballot-is-busted-before-the-blockchain-a-security-analysis-of-ac242526/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">3500d2a0-dce8-4542-a064-bfae7f6f1407</guid><title>Flash Boys 2.0: Frontrunning in Decentralized Exchanges, Miner Extractable Value, and Consensus Instability</title><link>https://apimade.com/podcasts/research/flash-boys-20-frontrunning-in-decentralized-exchanges-miner-extrac-95a16c6f/</link><pubDate>Tue, 25 Aug 2026 04:13:02 +0000</pubDate><description>Daian and colleagues measured decentralized-exchange ordering competition and documented bots repeatedly raising transaction fees to win profitable positions, while framing miners’ inclusion, exclusion and ordering power as extractable value. Detection engineers and protocol architects should treat transaction ordering as a security incentive, but the measured market was only a lower bound and the study demonstrated feasible reordering, not a consensus reorganization caused by miner extractable value.
A technical explanation of the paper's research question, method, reported findings and limitations. The measured market was valued in the millions of US dollars at the time of the experiment, but that amount was explicitly a lower bound rather than a complete accounting of extractable value. For the observed pure-revenue transactions, the median realized…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/4b331fec-bb87-492a-b822-54163199ef3f/ac5a7ddc-9e69-4acb-a48d-76a89bcee9e5.mp3" length="4645292" type="audio/mpeg"/><itunes:duration>290</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/flash-boys-20-frontrunning-in-decentralized-exchanges-miner-extrac-95a16c6f/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">5b0d7c7f-c458-49f4-9acc-8a0625ab1f62</guid><title>Extracting Training Data from Large Language Models</title><link>https://apimade.com/podcasts/research/extracting-training-data-from-large-language-models-e8873bce/</link><pubDate>Tue, 25 Aug 2026 04:12:20 +0000</pubDate><description>The study used black-box generation and ranking against GPT-2, confirming 604 unique memorized training examples among 1,800 inspected candidates and showing that a low average train-test loss gap did not prevent rare examples from having anomalously low loss. It proposed curation, deduplication, downstream filtering and model audits as complementary mitigations, but did not measure private-data extraction rates in deployed proprietary models.
A technical explanation of the paper's research question, method, reported findings and limitations. Among 1,800 inspected candidates, the researchers confirmed 604 unique memorized examples. The result was not explained away by the model's average behavior: a low average gap between training and test loss coexisted with rare examples having anomalously low…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/0c0f075f-d0e2-490c-9c78-1e37c78f08f9/b7536a18-8be8-4db2-a587-6d8811a089b7.mp3" length="4411052" type="audio/mpeg"/><itunes:duration>276</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/extracting-training-data-from-large-language-models-e8873bce/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">5e00d4ee-aeb3-488b-9e49-926f29004497</guid><title>Obfuscated Gradients Give a False Sense of Security: Circumventing Defenses to Adversarial Examples</title><link>https://apimade.com/podcasts/research/obfuscated-gradients-give-a-false-sense-of-security-circumventing-b1153154/</link><pubDate>Tue, 25 Aug 2026 04:11:39 +0000</pubDate><description>Researchers found that seven of nine selected ICLR 2018 defenses claiming white-box robustness relied on obfuscated gradients; adaptive attacks fully bypassed six and partially bypassed one within their stated threat models. After every defense change, attacks must adapt again; however, the evidence covers only selected non-certified defenses, while defenses with provable-security claims and a defense claiming only black-box security were excluded.
A technical explanation of the paper's research question, method, reported findings and limitations. Across the studied defenses, most relied on obfuscated gradients. Adaptive attacks completely circumvented all but one of those defenses under each defense’s original threat model, and partially circumvented the remaining defense. The result applies to the…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/ce17eee7-917d-4ec2-9354-02c1181824c1/af726d9e-4f24-4e38-8c71-b7a1de0e99f2.mp3" length="5436332" type="audio/mpeg"/><itunes:duration>340</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/obfuscated-gradients-give-a-false-sense-of-security-circumventing-b1153154/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">765edf12-3172-4a5e-a44e-a76e1aea9705</guid><title>Towards Evaluating the Robustness of Neural Networks</title><link>https://apimade.com/podcasts/research/towards-evaluating-the-robustness-of-neural-networks-9ce4c814/</link><pubDate>Tue, 25 Aug 2026 04:10:51 +0000</pubDate><description>Carlini and Wagner built targeted optimization attacks across multiple pixel-distance measures and achieved 100% success on distilled and undistilled MNIST and CIFAR-10 networks, tracing much of the apparent protection to scaled outputs and vanishing gradients. Model-security teams should test defenses with attacks adapted to their mechanisms, while recognizing that the evidence comes from white-box image-classification benchmarks whose pixel distances do not fully represent human similarity or operational security.
A technical explanation of the paper's research question, method, reported findings and limitations. The evaluation used the first 1,000 test images from both MNIST and CIFAR-10, plus 1,000 correctly classified ImageNet images. Across distilled and undistilled MNIST and CIFAR-10 networks, all three new attacks achieved 100% success. In an extreme ImageNet…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/df924fee-226b-4523-9bf9-58a9f94faca6/679ba019-020b-4bfc-bc72-fa6974c9bd82.mp3" length="4214060" type="audio/mpeg"/><itunes:duration>263</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/towards-evaluating-the-robustness-of-neural-networks-9ce4c814/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">0af53464-09fd-4f1c-8b18-96792b6f66d7</guid><title>Membership Inference Attacks Against Machine Learning Models</title><link>https://apimade.com/podcasts/research/membership-inference-attacks-against-machine-learning-models-3d2e6729/</link><pubDate>Tue, 25 Aug 2026 04:10:10 +0000</pubDate><description>Shokri and colleagues trained shadow models to learn how confidence outputs differ between training members and non-members, demonstrating membership inference through black-box prediction access across local and cloud models. For security teams, the results motivate leakage audits and consideration of differential privacy, but the balanced laboratory tests do not represent settings where membership is rare, and the study documented no victim harmed in the wild.
A technical explanation of the paper's research question, method, reported findings and limitations. Attack performance varied sharply by task. Across the tested Google models, precision ranged from 0.503 on one dataset to 0.935 on a purchase-record task. In the purchase experiments, dividing the prediction problem into more output classes, with fewer…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5793f473-0ac9-468a-a460-f06a6d14952d/37ebd3f8-64b8-4d42-8da3-c17bf49e5961.mp3" length="3993644" type="audio/mpeg"/><itunes:duration>250</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/membership-inference-attacks-against-machine-learning-models-3d2e6729/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">7ee40487-6eb7-4186-a57f-dfc2d4a47d87</guid><title>Stealing Machine Learning Models via Prediction APIs</title><link>https://apimade.com/podcasts/research/stealing-machine-learning-models-via-prediction-apis-c2031833/</link><pubDate>Tue, 25 Aug 2026 04:09:30 +0000</pubDate><description>For multiclass logistic regression, prediction API responses enabled exact parameter extraction, while the paper distinguished this from improper extraction that duplicates useful behavior. Extracted models in the evaluated online Amazon and BigML case studies agreed with every tested input. Preprocessing and response structure exposed feature information. The work did not evaluate ensembles, contemporary deep architectures, distributed attackers, adaptive defenses, or production-grade monitoring.
A technical explanation of the paper's research question, method, reported findings and limitations. The Amazon Digits model was extracted exactly with 650 queries in about 70 seconds. Across the evaluated Amazon and BigML online cases, the extracted models agreed with their targets on every tested input. That is strong agreement within those tests, but it…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5e9dabec-2d90-4c02-9b96-460e89cbb31d/e353e3c5-fc58-451d-b71a-cb46c882a73d.mp3" length="4879532" type="audio/mpeg"/><itunes:duration>305</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/stealing-machine-learning-models-via-prediction-apis-c2031833/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">793aa871-5b44-45ac-bc37-592e58911522</guid><title>Deep Learning with Differential Privacy</title><link>https://apimade.com/podcasts/research/deep-learning-with-differential-privacy-96a1d5c1/</link><pubDate>Tue, 25 Aug 2026 04:08:49 +0000</pubDate><description>Abadi and colleagues made neural-network training differentially private by clipping each example’s gradient, adding calibrated Gaussian noise, and tracking accumulated privacy loss more tightly across training steps. Security and privacy teams can treat this as a design pattern, but the guarantee was mainly example-level and the benchmark experiments were neither production deployments nor audits of the full training pipeline.
A technical explanation of the paper's research question, method, reported findings and limitations. In one fixed training setup, after 100 epochs, the moments accountant reported epsilon 1.26, compared with 9.34 from the baseline calculation under the same sampling and noise parameters. This demonstrates a tighter upper-bound calculation for the repeated…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/9c21742e-7ca4-47b6-894b-3f47548ba649/f261edb8-35ac-4e03-90a5-09bafdb84e9d.mp3" length="4388012" type="audio/mpeg"/><itunes:duration>274</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/deep-learning-with-differential-privacy-96a1d5c1/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">c090ef78-ae10-4aa3-9c6f-2d1805fd6f71</guid><title>Towards Making Systems Forget with Machine Unlearning</title><link>https://apimade.com/podcasts/research/towards-making-systems-forget-with-machine-unlearning-08e2b520/</link><pubDate>Tue, 25 Aug 2026 04:08:11 +0000</pubDate><description>Cao and Yang made selected training records removable by storing reusable sums, then subtracting a record’s contribution; across the evaluated systems, this was sometimes much faster than retraining and reversed constructed poisoning effects. Detection engineers can treat unlearning as an incident-recovery primitive, but the study mostly checked prediction agreement and attack repair, not equivalent model distributions or privacy extraction, and it left record identification to other processes.
A technical explanation of the paper's research question, method, reported findings and limitations. The evaluation covered several systems spanning several learning algorithms. Every evaluated system was shown vulnerable either through a reproduced inference attack or a constructed poisoning attack. Speed varied sharply. Zozzle deletion finished in under a…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/1583432a-fd24-4cc6-950a-6ce726e99838/6851205c-88a1-43b0-9836-9b4053176e02.mp3" length="5689772" type="audio/mpeg"/><itunes:duration>356</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/towards-making-systems-forget-with-machine-unlearning-08e2b520/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">3c85206b-80dd-40f4-ad0c-2d1bbd172bea</guid><title>Model Inversion Attacks That Exploit Confidence Information and Basic Countermeasures</title><link>https://apimade.com/podcasts/research/model-inversion-attacks-that-exploit-confidence-information-and-ba-3dd04dca/</link><pubDate>Tue, 25 Aug 2026 04:07:30 +0000</pubDate><description>Fredrikson, Jha, and Ristenpart tested model inversion against confidence-bearing decision trees and face classifiers, inferring sensitive survey responses and producing identity-linked face representatives. Security teams should treat confidence precision as a privacy-relevant design choice and test whether coarser outputs help, but the face images were not recovered training photos and the evaluated countermeasures were explicitly basic.
A technical explanation of the paper's research question, method, reported findings and limitations. With access to the internal decision-tree details—the white-box setting—the attack achieved perfect precision for positive sensitive responses in both datasets. In other words, the evaluated positive predictions produced no false positives. For…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/40c6ca17-0c60-44c2-afd6-06b4c20d1374/5275bd4d-5006-4c27-bcd1-71146adc411e.mp3" length="4738604" type="audio/mpeg"/><itunes:duration>296</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/model-inversion-attacks-that-exploit-confidence-information-and-ba-3dd04dca/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">984cdb73-3a77-4ebe-ab5c-ec55fcccfe4e</guid><title>Outside the Closed World: On Using Machine Learning for Network Intrusion Detection</title><link>https://apimade.com/podcasts/research/outside-the-closed-world-on-using-machine-learning-for-network-int-7baec4ce/</link><pubDate>Tue, 25 Aug 2026 04:06:45 +0000</pubDate><description>Sommer and Paxson explain why machine-learning network intrusion detectors often work better at finding activity resembling known examples than at identifying genuinely novel attacks from normal-traffic models. Detection teams should define a narrow threat model, validate with real traffic and independent ground truth, and compare against simpler rules; because the work is conceptual and largely intuitive, it does not prove that all machine-learning detectors fail.
A technical explanation of the paper's research question, method, reported findings and limitations. The analysis concludes that machine learning is stronger at finding activity similar to observed examples than at discovering a meaningful, genuinely novel attack from a model of normal traffic alone. Given examples of activity of interest, a learning system…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/8a2eee4f-fc16-4acb-934f-b83d2acd5343/cafdbaf9-cb31-48f6-b167-20a2ae544747.mp3" length="5332652" type="audio/mpeg"/><itunes:duration>333</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/outside-the-closed-world-on-using-machine-learning-for-network-int-7baec4ce/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">17b48a23-93d4-4809-aa21-135f092ed816</guid><title>Can Machine Learning Be Secure?</title><link>https://apimade.com/podcasts/research/can-machine-learning-be-secure-ceb6130c/</link><pubDate>Tue, 25 Aug 2026 04:05:59 +0000</pubDate><description>Barreno and colleagues organized attacks on machine-learning systems by whether adversaries alter training or probe the learner, how broadly they target inputs, and whether they cause integrity or availability failures; they also analyzed how malicious training points can shift a simple online detector. Security teams should treat training and query interfaces as attack surfaces, but the proposed defenses were speculative and were not validated on realistic learners.
A technical explanation of the paper's research question, method, reported findings and limitations. In the mathematical case, the optimal attacker repeatedly places a malicious point where the line toward the target reaches the detector’s current acceptance edge. Each accepted point shifts the average, allowing further movement. For large displacement…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/664848c5-e364-45c9-b59d-cc89df89e8b2/2ed744f0-cae7-4d52-ae39-3da859c8118b.mp3" length="5186732" type="audio/mpeg"/><itunes:duration>324</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/can-machine-learning-be-secure-ceb6130c/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">18fe0121-2dcc-4466-9c26-55c3f72b3c64</guid><title>Bulletproofs: Short Proofs for Confidential Transactions and More</title><link>https://apimade.com/podcasts/research/bulletproofs-short-proofs-for-confidential-transactions-and-more-add21151/</link><pubDate>Tue, 25 Aug 2026 04:05:18 +0000</pubDate><description>Bulletproofs compresses range proofs without a trusted setup: proof bytes grow logarithmically, including when same-width proofs are aggregated, while proving and verification work remain linear. For confidential-transaction teams, that can reduce permanent ledger data, but deployments must price verification and denial-of-service cost, bind every public input into Fiat-Shamir transcripts, and plan around the scheme’s discrete-logarithm and long-term quantum risks.
A technical explanation of the paper's research question, method, reported findings and limitations. Compact proof bytes do not mean compact verification. As a range’s bit width grows, its proof adds only logarithmically more elements—in plain terms, proof length grows much more slowly than the statement—while proving and verification grow in step with that…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/7dd47f2c-2672-48e6-bc72-76250f740fad/e6e0c824-981d-48de-a407-7db2492b3071.mp3" length="6250412" type="audio/mpeg"/><itunes:duration>391</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/bulletproofs-short-proofs-for-confidential-transactions-and-more-add21151/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">50c8ccbb-eca9-4034-b197-081e2e2edeb1</guid><title>Zerocash: Decentralized Anonymous Payments from Bitcoin</title><link>https://apimade.com/podcasts/research/zerocash-decentralized-anonymous-payments-from-bitcoin-e14c1367/</link><pubDate>Tue, 25 Aug 2026 04:04:37 +0000</pubDate><description>Zerocash lets a public ledger enforce ownership, balance, and non-double-spending while hiding payment origin, destination, and amount, and was evaluated through a research prototype and modeled network. It supports ledger-level private validation, not end-to-end anonymity or production readiness; its guarantees depend on cryptographic primitives, correct circuitry, trusted setup, and security proofs, and exclude network traffic, wallet endpoints, exchanges, and human payment behavior.
A technical explanation of the paper's research question, method, reported findings and limitations. On the reported desktop, constructing a pour took about 2 minutes, while checking it took 5.7 milliseconds. The transaction measured 996 bytes plus auxiliary information. In that environment, pour construction was far more demanding than verification.…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5a9baabd-1e12-44e5-8a5e-9cb3567eb16c/38bca873-6cf2-4880-bf37-a9954537b887.mp3" length="4268972" type="audio/mpeg"/><itunes:duration>267</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/zerocash-decentralized-anonymous-payments-from-bitcoin-e14c1367/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">0df4b385-c704-4791-b070-bc8bf8a79113</guid><title>The Web Never Forgets: Persistent Tracking Mechanisms in the Wild</title><link>https://apimade.com/podcasts/research/the-web-never-forgets-persistent-tracking-mechanisms-in-the-wild-cf2bbd79/</link><pubDate>Tue, 25 Aug 2026 04:03:58 +0000</pubDate><description>Acar and colleagues measured canvas fingerprinting, evercookie respawning and cookie synchronization in large web crawls, finding that separate identifiers could restore or connect tracking state, while third-party-cookie blocking reduced but did not eliminate synchronization. Browser and privacy teams should coordinate state clearing and layer defenses, but the desktop Firefox, homepage-heavy dataset and unobserved back-end mergers limit claims about broader environments.
A technical explanation of the paper's research question, method, reported findings and limitations. The large crawl detected canvas fingerprinting on more than 5.5 percent of the measured homepages. About 95 percent of the detected scripts were associated with AddThis, so deployment was heavily concentrated in one provider within this dataset. Commercial…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/251d7bf2-92a8-48e4-827c-04c41fc34bc6/0c434fd5-ccaf-4e99-8907-764988119b69.mp3" length="4849964" type="audio/mpeg"/><itunes:duration>303</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-web-never-forgets-persistent-tracking-mechanisms-in-the-wild-cf2bbd79/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">4deb2ffa-622d-452f-abfb-abc4cb3d7850</guid><title>RAPPOR: Randomized Aggregatable Privacy-Preserving Ordinal Response</title><link>https://apimade.com/podcasts/research/rappor-randomized-aggregatable-privacy-preserving-ordinal-response-3cf77f34/</link><pubDate>Tue, 25 Aug 2026 04:03:18 +0000</pubDate><description>RAPPOR lets a collector estimate population statistics from values randomized on each client, reducing access to unmodified data, but useful accuracy can demand enormous samples. For security telemetry teams, it offers a way to reduce reliance on a trusted central collector; rare or changing values, correlated collection, candidate-list construction, and implementation choices can still undermine utility or longitudinal privacy.
A technical explanation of the paper's research question, method, reported findings and limitations. The privacy and accuracy results need to be considered together. For an unchanged value, arbitrarily many reports may expose the remembered randomized pattern, but no more; the researchers derived a finite privacy bound across repeated collection for that…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/ad1b8513-b3c8-4423-81f1-3e796860dc0b/c93437e1-c932-4b4b-bd4f-37be0eb7a5e7.mp3" length="5258540" type="audio/mpeg"/><itunes:duration>329</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/rappor-randomized-aggregatable-privacy-preserving-ordinal-response-3cf77f34/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">c1eb8975-0989-4ec7-a9c4-4860a9b65911</guid><title>Pinocchio: Nearly Practical Verifiable Computation</title><link>https://apimade.com/podcasts/research/pinocchio-nearly-practical-verifiable-computation-927985cd/</link><pubDate>Tue, 25 Aug 2026 04:02:38 +0000</pubDate><description>Pinocchio compiled a restricted subset of C into pairing-based proofs that remained 288 bytes regardless of computation size, and typically let anyone verify seven evaluated applications in about 10 milliseconds. For security engineering, public verification can reduce trust in outsourced workers, but the prototype was not a drop-in cloud verifier: it required function-specific setup, used large evaluation keys, supported constrained programs, and three applications did not beat native execution.
A technical explanation of the paper's research question, method, reported findings and limitations. Each proof was a constant 288 bytes, independent of the computation and the sizes of its inputs and outputs. Across the evaluated C applications, verification typically took about 10 milliseconds, and some parameter settings checked faster than running the…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/8120379f-d302-4542-a0af-32a0fe5787f8/695747b5-fdb2-43c8-9691-5f95a6e5e9ce.mp3" length="4317740" type="audio/mpeg"/><itunes:duration>270</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/pinocchio-nearly-practical-verifiable-computation-927985cd/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">d4898e08-6f25-4deb-b8d0-aa1e56133aa9</guid><title>Path ORAM: An Extremely Simple Oblivious RAM Protocol</title><link>https://apimade.com/podcasts/research/path-oram-an-extremely-simple-oblivious-ram-protocol-52ee608c/</link><pubDate>Tue, 25 Aug 2026 04:01:59 +0000</pubDate><description>Stefanov and colleagues present a tree protocol in which the server stores encrypted real and dummy blocks, while the client stores a position map and stash. Each logical access remaps the target, reads its old full path, updates the block, and writes back a padded, re-encrypted path. The evaluation does not cover independent cloud-service deployment, multi-tenant concurrency, or end-to-end application privacy, and timing leakage is explicitly excluded.
A technical explanation of the paper's research question, method, reported findings and limitations. The core access procedure is compact, but compact control flow does not remove its resource costs. A non-recursive operation reads and writes a number of blocks proportional to bucket capacity and to the logarithm of the number of stored blocks. Recursively…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/76c67805-f3f7-4593-bd47-1c3c71174154/1e8d9f21-30c9-46d8-a2f0-782c1ee48c00.mp3" length="6149420" type="audio/mpeg"/><itunes:duration>384</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/path-oram-an-extremely-simple-oblivious-ram-protocol-52ee608c/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">6dbdef98-d893-4a80-90c9-25a948a9c48d</guid><title>Robust De-anonymization of Large Sparse Datasets</title><link>https://apimade.com/podcasts/research/robust-de-anonymization-of-large-sparse-datasets-8bf5d0d2/</link><pubDate>Tue, 25 Aug 2026 04:01:19 +0000</pubDate><description>Narayanan and Shmatikov matched sparse Netflix rating histories against outside clues; in one noisy 8-rating experiment, 99 percent of released records were uniquely identified, and linked profiles exposed attributes absent from those clues. Security teams should treat row-level behavioral releases as linkable and use risk-tested controls, but that rate is dataset-specific and the small IMDb test lacked verified identities.
A technical explanation of the paper's research question, method, reported findings and limitations. In one experiment, the system received 8 movie ratings, some of which could be completely wrong, while the rating dates could be imprecise. It uniquely identified nearly all records in the released dataset. That is a result for this particular dataset and…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/df53654d-460d-4abd-b5cf-c5d9d820e506/1b2cb4cb-86f9-4287-a1dd-63c3d0517513.mp3" length="5318444" type="audio/mpeg"/><itunes:duration>332</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/robust-de-anonymization-of-large-sparse-datasets-8bf5d0d2/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">3d6606f7-8cf4-4fb6-964f-62f385c6c996</guid><title>Attribute-Based Encryption for Fine-Grained Access Control of Encrypted Data</title><link>https://apimade.com/podcasts/research/attribute-based-encryption-for-fine-grained-access-control-of-encr-b0f1b5a3/</link><pubDate>Tue, 25 Aug 2026 04:00:38 +0000</pubDate><description>Vipul Goyal and colleagues introduced a key-policy form of attribute-based encryption in which ciphertext attributes are tested against access policies embedded in decryption keys, with resistance to combining individually unauthorized keys. The design may suit encrypted audit logs or targeted distribution, but deployment requires separate solutions for revocation, exposed attributes, compromised issuers, and other lifecycle gaps the work did not solve.
A technical explanation of the paper's research question, method, reported findings and limitations. The construction ties key components together so that users cannot combine multiple keys, each unauthorized on its own, into a newly authorized decryption capability. That provides the intended collusion resistance. It also supports local delegation: a key…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/be77ed1b-3f09-4a56-bae5-8a7780198502/d1aded44-8247-4573-83c5-e3c896ac2cd7.mp3" length="4257452" type="audio/mpeg"/><itunes:duration>266</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/attribute-based-encryption-for-fine-grained-access-control-of-encr-b0f1b5a3/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">fdddc164-e144-4c04-a883-ded69d931045</guid><title>Calibrating Noise to Sensitivity in Private Data Analysis</title><link>https://apimade.com/podcasts/research/calibrating-noise-to-sensitivity-in-private-data-analysis-84ffbaeb/</link><pubDate>Tue, 25 Aug 2026 03:59:52 +0000</pubDate><description>Privacy is defined through transcript probabilities against arbitrary adversaries and auxiliary knowledge, with one-row adjacency but no specified person, household, device, document, or user-level contribution model. Independent Laplace noise scaled to vector-query sensitivity divided by epsilon provides the guarantee. Epsilon is a policy parameter; the theory reports no software implementation, production deployment, performance evaluation, or empirical privacy audit and does not analyze floating-point, random-number, timing, or metadata channels.
A technical explanation of the paper's research question, method, reported findings and limitations. For a bounded count of binary contributions, the Laplace noise scale is the sensitivity divided by epsilon. The analysis also establishes that histograms, contingency tables, and covariance-style vector queries can have sensitivity that does not grow with the…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/0f99a1cf-e6bf-4916-8876-4a3477a2b68a/c120d1b3-8696-4a87-997b-46b3983621bb.mp3" length="4518572" type="audio/mpeg"/><itunes:duration>282</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/calibrating-noise-to-sensitivity-in-private-data-analysis-84ffbaeb/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">45582744-d0b4-45da-9a9d-e4a1459981ce</guid><title>Understanding the Mirai Botnet</title><link>https://apimade.com/podcasts/research/understanding-the-mirai-botnet-3d6498af/</link><pubDate>Tue, 25 Aug 2026 03:59:12 +0000</pubDate><description>Antonakakis and colleagues combined Internet-scale sensing, honeypots, malware, DNS, command observations and victim traces to reconstruct how Mirai found exposed Telnet services, tried hard-coded credentials and received distributed-denial-of-service orders. For defenders, the evidence supports closing management services by default and maintaining secure update and end-of-life processes, but it covers only visible activity and selected traces—not every device, operator or harm.
A technical explanation of the paper's research question, method, reported findings and limitations. During its first measured day, the outbreak infected about 64,500 devices. The estimated population later settled in the hundreds of thousands and briefly approached 600,000. Infections were geographically concentrated, while the device mix reflected both…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/b380d71d-c910-40df-abf7-ef587d2168e4/4fc3ed66-be60-43b9-9ed6-6f4027a450e8.mp3" length="3769772" type="audio/mpeg"/><itunes:duration>236</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/understanding-the-mirai-botnet-3d6498af/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">c1866142-4188-4a28-90a3-a22183e3c505</guid><title>Security Enhanced (SE) Android: Bringing Flexible MAC to Android</title><link>https://apimade.com/podcasts/research/security-enhanced-se-android-bringing-flexible-mac-to-android-680bbf18/</link><pubDate>Tue, 25 Aug 2026 03:58:33 +0000</pubDate><description>Smalley and Craig integrated SELinux policy across Android, including Binder, and showed in tested exploit cases that obtaining the root user identity could still leave a process confined without broader SELinux authority. Android platform and vendor security teams can use that model to narrow allowed operations, but policy cannot block actions it permits or generally repair kernel flaws, so the results do not establish an ecosystem-wide compromise-prevention rate.
A technical explanation of the paper's research question, method, reported findings and limitations. Across the tested privilege-escalation cases, two outcomes repeated: policy checks blocked individual exploit steps, and processes with root as their user identity still remained confined. For GingerBreak, checks prevented steps such as creating the required…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/8aceba12-e94e-499f-bf18-d7ef5cc9d809/c6df6271-05f3-43c9-863d-c66533bd7cd5.mp3" length="5197100" type="audio/mpeg"/><itunes:duration>325</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/security-enhanced-se-android-bringing-flexible-mac-to-android-680bbf18/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">0fb85da3-e93c-43f9-a344-56a3112364ef</guid><title>Cross-VM Side Channels and Their Use to Extract Private Keys</title><link>https://apimade.com/podcasts/research/cross-vm-side-channels-and-their-use-to-extract-private-keys-262aaae2/</link><pubDate>Tue, 25 Aug 2026 03:57:54 +0000</pubDate><description>Zhang and colleagues used Prime-and-Probe measurements of L1 instruction-cache activity between co-resident virtual machines, then classified noisy traces and searched a reduced candidate set to recover an ElGamal private key in a controlled Xen experiment. The result did not require exploiting the hypervisor or directly reading victim memory, but depended on favorable laboratory conditions, repeated decryptions, known victim code, and a secret-dependent implementation; public-cloud placement was not demonstrated.
A technical explanation of the paper's research question, method, reported findings and limitations. The victim ran GnuPG using libgcrypt, with a 457-bit private exponent—the secret value used in the cryptographic calculation. In one Xen scheduler setting, the attacker ran hundreds of millions of Prime-and-Probe trials over several hours. The online trace…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/83bffb09-7c64-491d-bee1-11820d6c1f4a/6ba41dd9-3d49-46fa-8fdf-a020badaefca.mp3" length="4250924" type="audio/mpeg"/><itunes:duration>266</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/cross-vm-side-channels-and-their-use-to-extract-private-keys-262aaae2/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">a2fc845c-d772-4977-9f26-c63650f92b73</guid><title>Comprehensive Experimental Analyses of Automotive Attack Surfaces</title><link>https://apimade.com/podcasts/research/comprehensive-experimental-analyses-of-automotive-attack-surfaces-6f513cfb/</link><pubDate>Tue, 25 Aug 2026 03:57:14 +0000</pubDate><description>Checkoway and colleagues built working paths into automotive networks through crafted media, a dealership service device, Bluetooth, and cellular telematics, then demonstrated remote control and surveillance capabilities after compromise. Vehicle and fleet defenders should restrict interfaces, strengthen authentication, monitor behavior, and protect updates, while recognizing that the experiments covered a single unnamed model and a pair of equivalent vehicles, not prevalence or portability across manufacturers.
A technical explanation of the paper's research question, method, reported findings and limitations. The media path began with a crafted audio file. An unchecked length in the player’s parser let the file cause code execution, and that code could send traffic onto the vehicle’s internal network. The dealership path exploited an unauthenticated service on the…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/0aceb7b8-d775-463f-949f-449b0f8fb506/f8996347-d999-44ed-804d-746e01f95cd2.mp3" length="4457132" type="audio/mpeg"/><itunes:duration>279</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/comprehensive-experimental-analyses-of-automotive-attack-surfaces-6f513cfb/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">bb10d521-1014-41d8-b849-ce0abb81c717</guid><title>Android Permissions Demystified</title><link>https://apimade.com/podcasts/research/android-permissions-demystified-fc1565da/</link><pubDate>Tue, 25 Aug 2026 03:56:33 +0000</pubDate><description>By instrumenting Android 2.2 and comparing compiled app calls with manifest requests, the researchers estimated that 30.4 percent of 795 fully handled Android Market apps requested unnecessary permissions. For mobile security teams, that supports better permission mapping and documentation, but the corpus was a 2011 snapshot, complex reflection was unresolved, and the analysis never quantified how many overprivileged apps it missed.
A technical explanation of the paper's research question, method, reported findings and limitations. The platform testing reached about 85 percent of the Android API and identified permission requirements for 1,259 methods. Android documentation listed only 78 methods, and the tests also uncovered documentation errors. That gap supports the researchers’…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/eea81621-cb12-4520-a88c-cde79d063015/accbf9c7-6bf9-4a41-9b0f-e783ffedeca9.mp3" length="4430252" type="audio/mpeg"/><itunes:duration>277</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/android-permissions-demystified-fc1565da/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">fe640e4e-d917-4550-9122-85162f8c7ada</guid><title>TaintDroid: An Information-Flow Tracking System for Realtime Privacy Monitoring on Smartphones</title><link>https://apimade.com/podcasts/research/taintdroid-an-information-flow-tracking-system-for-realtime-privac-28a19222/</link><pubDate>Tue, 25 Aug 2026 03:55:53 +0000</pubDate><description>Enck and colleagues modified Android to attach labels to sensitive data and follow explicit flows across variables, files, messages and selected libraries, flagging 68 potentially misused flows across 20 of 30 tested apps. For detection and mobile-security teams, it demonstrates why observing data use can add context beyond permissions, but the Android 2.1-era, manually exercised sample and incomplete native and control-flow tracking limit generalisation.
A technical explanation of the paper's research question, method, reported findings and limitations. On CPU-bound microbenchmarks, the prototype ran slower. Its broad system summary estimated memory overhead at about 4.4 percent, while interactive applications reportedly had negligible perceived delay. The cost was uneven: communication between processes…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/76b9e000-3af4-40a1-851e-db310430ef73/751325d3-c472-4d91-afec-468ff811051a.mp3" length="4926764" type="audio/mpeg"/><itunes:duration>308</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/taintdroid-an-information-flow-tracking-system-for-realtime-privac-28a19222/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">dcc8c95e-8414-4e1f-a064-fdaf0bb40f04</guid><title>Experimental Security Analysis of a Modern Automobile</title><link>https://apimade.com/podcasts/research/experimental-security-analysis-of-a-modern-automobile-f3dfc1d5/</link><pubDate>Tue, 25 Aug 2026 03:55:19 +0000</pubDate><description>Using custom CAN capture, replay and fuzzing tools on two same-model 2009 cars, researchers showed that unauthenticated internal messages could falsify displays, manipulate body functions, disrupt engines, and engage or release brakes, while compromised components could bridge network separation and persist. Cybersecurity teams should therefore test post-compromise containment, detection, fail-safe behavior, and recovery, but the study assumed internal-network access and did not establish remote exploitability or prevalence across vehicle platforms.
A technical explanation of the paper's research question, method, reported findings and limitations. The tested controls provided limited resistance once the internal network was exposed. Diagnostic and reprogramming protections were often unused or could be bypassed. For one brake controller, the researchers recovered a 16-bit challenge-response key in…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/dd813e7a-2765-42b7-84fd-71d452a1ffd3/62fd72ba-3495-4732-8549-1fa3e8416600.mp3" length="4322732" type="audio/mpeg"/><itunes:duration>270</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/experimental-security-analysis-of-a-modern-automobile-f3dfc1d5/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">00860c8e-d67d-4824-9f66-247d1dfcd63a</guid><title>Hey, You, Get Off of My Cloud: Exploring Information Leakage in Third-Party Compute Clouds</title><link>https://apimade.com/podcasts/research/hey-you-get-off-of-my-cloud-exploring-information-leakage-in-third-23c4deca/</link><pubDate>Tue, 25 Aug 2026 03:54:34 +0000</pubDate><description>Ristenpart and colleagues showed that an ordinary cloud customer could map EC2 placement, launch probe virtual machines, sometimes reach physical-host co-residence with a chosen target, and demonstrate controlled cross-VM leakage rather than theft from an unrelated customer. Cloud security teams should treat shared hardware as an observable attack surface, but the measured placement economics were deployment-specific and no real customer secret was extracted.
A technical explanation of the paper's research question, method, reported findings and limitations. The broad launch strategy achieved co-residence for only a small percentage of eligible targets. In a focused locality experiment, 20 attacker probes reached roughly 40 percent probability of sharing a host with one recently launched victim, and additional…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/945edd3a-fee5-4271-8a0a-16ef094b5bc7/42fd7c72-a8cd-424c-8917-8dfb9f75131b.mp3" length="4976300" type="audio/mpeg"/><itunes:duration>311</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/hey-you-get-off-of-my-cloud-exploring-information-leakage-in-third-23c4deca/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">73471bc0-1270-432c-b726-37dd3834ca98</guid><title>in-toto: Providing farm-to-table guarantees for bits and bytes</title><link>https://apimade.com/podcasts/research/in-toto-providing-farm-to-table-guarantees-for-bits-and-bytes-005fd30f/</link><pubDate>Tue, 25 Aug 2026 03:53:55 +0000</pubDate><description>in-toto has project owners sign a supply-chain policy, authorized actors sign evidence for each step, and clients check a delivered artifact against both. Security teams can use thresholds and role separation to limit a compromised authorized actor, but the model trusts owner and functionary keys, and the evaluation did not test long-term organizational operation.
A technical explanation of the paper's research question, method, reported findings and limitations. Most incidents in the classified set involved no key compromise. For the selected incidents, estimated coverage across the evaluated layouts ranged from most to all of the cases. These estimates describe how the policies might have covered those cases under…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5e19250e-f51c-4618-a0ef-6f0405b8f522/e7da28dd-b6b5-4153-85d0-231ac5391af7.mp3" length="4058924" type="audio/mpeg"/><itunes:duration>254</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/in-toto-providing-farm-to-table-guarantees-for-bits-and-bytes-005fd30f/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">18ed4ca1-cade-4078-9d82-87eab8222307</guid><title>Online Tracking: A 1-Million-Site Measurement and Analysis</title><link>https://apimade.com/podcasts/research/online-tracking-a-1-million-site-measurement-and-analysis-3dfab3f2/</link><pubDate>Tue, 25 Aug 2026 03:53:12 +0000</pubDate><description>Englehardt and Narayanan used a full Firefox-based crawl of the Alexa top 1 million sites to measure cookies, third parties, cookie syncing and browser fingerprinting at web scale. Security and privacy teams can reuse that measurement mindset, but the results are a lower bound: the crawl visited only homepages, performed no interaction or login, used one US East vantage, and omitted known techniques.
A technical explanation of the paper's research question, method, reported findings and limitations. The census found more than 81,000 third parties across the sites it visited, yet only 123 appeared on more than 1% of sites. Tracking infrastructure therefore had a very long tail: many parties appeared rarely, while a small group reached broadly. Mapping…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/f15f014f-05f9-4811-b7c7-465d6f780a90/bbb5538e-9ad6-453d-a7b1-74660585d32b.mp3" length="5013932" type="audio/mpeg"/><itunes:duration>313</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/online-tracking-a-1-million-site-measurement-and-analysis-3dfab3f2/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">eecfd170-e534-4ac9-8363-669c3054910d</guid><title>A Comprehensive Formal Security Analysis of OAuth 2.0</title><link>https://apimade.com/podcasts/research/a-comprehensive-formal-security-analysis-of-oauth-20-b026dbdf/</link><pubDate>Tue, 25 Aug 2026 03:52:33 +0000</pubDate><description>Fett, Küsters, and Schmitz modeled the OAuth grant types together, identified several attack patterns, and checked variants in real software and a website. Identity teams can apply the proposed issuer, redirect, state, and user-intent checks during design review, but the proof depends on stated assumptions and does not cover implementation code, token expiry, logout, or revocation.
A technical explanation of the paper's research question, method, reported findings and limitations. One attack depended on an HTTP 307 redirect. Because that redirect preserves the submitted request body, it could forward an identity-provider credential submission to a relying party. The repair was to use a redirect such as 303, which does not preserve that…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/9e2496f7-30d1-435b-8576-bb16282d26c3/5a919242-039b-4c10-8a8b-254ff67f7184.mp3" length="6046892" type="audio/mpeg"/><itunes:duration>378</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/a-comprehensive-formal-security-analysis-of-oauth-20-b026dbdf/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">cb9c57f2-51a4-4c0d-b44c-a603e734d039</guid><title>Imperfect Forward Secrecy: How Diffie-Hellman Fails in Practice</title><link>https://apimade.com/podcasts/research/imperfect-forward-secrecy-how-diffie-hellman-fails-in-practice-5fb3ddaa/</link><pubDate>Tue, 25 Aug 2026 03:51:54 +0000</pubDate><description>Adrian and colleagues demonstrated Logjam: an active TLS downgrade that forced export-grade ephemeral Diffie-Hellman, then used reusable prime-specific computation to compromise sessions; their precomputation enabled attacks on more than 7 percent of Alexa Top Million HTTPS sites. Defenders should remove export suites and weak finite-field groups, but the broader 1024-bit nation-state scenario remained an uncertain extrapolation rather than a demonstrated computation or attribution.
A technical explanation of the paper's research question, method, reported findings and limitations. The HTTPS measurements found that 8.4% of Alexa Top Million sites were vulnerable to Logjam. After completing the reusable computation, the team could actively compromise more than 7 percent of sites in that population. The investigation also uncovered…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/840234ca-02fd-462f-be3f-fc707f5aa405/093c69d9-51bd-4705-8119-623c69c4d42e.mp3" length="5434412" type="audio/mpeg"/><itunes:duration>340</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/imperfect-forward-secrecy-how-diffie-hellman-fails-in-practice-5fb3ddaa/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">8b79e393-e98f-4346-a948-966c68c8a448</guid><title>ZMap: Fast Internet-Wide Scanning and its Security Applications</title><link>https://apimade.com/podcasts/research/zmap-fast-internet-wide-scanning-and-its-security-applications-1f36c4b1/</link><pubDate>Tue, 25 Aug 2026 03:51:09 +0000</pubDate><description>Durumeric, Wustrow and Halderman built a stateless scanner that made comprehensive, single-port public-IPv4 surveys practical on a commodity machine; on their gigabit system, a scan took about 44 minutes. For exposure teams, that enables repeatable discovery, but an address response does not establish the application or owner, and a single probe can miss responsive web hosts.
A technical explanation of the paper's research question, method, reported findings and limitations. On the authors’ gigabit test system, a single-probe scan of public IPv4 took about 44 minutes. Controlled trials estimated that a single probe found nearly all responsive hosts, so high speed did not mean perfect completeness. For comparable single-port…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/e8b27c85-32dc-4853-9b52-75b2e0dc29ff/1878e7a7-c004-4ee0-b31d-d0e9b9cfda53.mp3" length="4836140" type="audio/mpeg"/><itunes:duration>302</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/zmap-fast-internet-wide-scanning-and-its-security-applications-1f36c4b1/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">d11cb8d4-f155-403a-a6a1-27d150f4f13d</guid><title>On Breaking SAML: Be Whoever You Want to Be</title><link>https://apimade.com/podcasts/research/on-breaking-saml-be-whoever-you-want-to-be-baf7f4fa/</link><pubDate>Tue, 25 Aug 2026 03:50:29 +0000</pubDate><description>Using systematically generated structural SAML message variants, the researchers examined how signature verification and claim processing may select different XML nodes. SAML integrations should preserve signed-element provenance and pass only content established as signed to application logic. Because the evaluation covered particular systems and generated variants, its findings do not establish exposure beyond the evaluated setting.
A technical explanation of the paper's research question, method, reported findings and limitations. The researchers found that most systems in the evaluated sample were vulnerable. Most accepted refined wrapping attacks, and a smaller group accepted signature-exclusion variants. A minority resisted every tested variant. Vulnerability was common in this…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/a914b3c4-321a-4b02-928f-6fa2f6ea3c33/5463a6dc-9b35-47d3-b8ae-852a615ce2e1.mp3" length="3970604" type="audio/mpeg"/><itunes:duration>248</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/on-breaking-saml-be-whoever-you-want-to-be-baf7f4fa/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">ad5b03ba-bcfd-4aa7-939b-e8c4849c46a5</guid><title>Mining Your Ps and Qs: Detection of Widespread Weak Keys in Network Devices</title><link>https://apimade.com/podcasts/research/mining-your-ps-and-qs-detection-of-widespread-weak-keys-in-network-a87a8c16/</link><pubDate>Tue, 25 Aug 2026 03:49:51 +0000</pubDate><description>Using Internet-wide TLS and SSH measurements, Heninger and colleagues found shared RSA factors and repeated signing values that exposed private keys, while widespread reuse also reflected manufacturer defaults. Security teams should block key generation until randomness is ready and regenerate weak keys, but the scan covered only publicly reachable IPv4 endpoints on selected ports and device attribution was strongest for recognizable clusters.
A technical explanation of the paper's research question, method, reported findings and limitations. Two results turn duplication into concrete private-key exposure. Shared primes let the team recover RSA private keys used by 0.50% of TLS hosts in the scan, with a smaller affected share among SSH hosts. Repeated one-time signing values exposed private keys…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/15ff3654-6984-4a95-8f1c-dcf5af1f5124/601ead46-5ee0-4f8c-9432-4ff1730cddda.mp3" length="5661740" type="audio/mpeg"/><itunes:duration>354</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/mining-your-ps-and-qs-detection-of-widespread-weak-keys-in-network-a87a8c16/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">f179bd5a-7976-41a1-9277-457c0e90d158</guid><title>The Most Dangerous Code in the World: Validating SSL Certificates in Non-Browser Software</title><link>https://apimade.com/podcasts/research/the-most-dangerous-code-in-the-world-validating-ssl-certificates-i-58faef88/</link><pubDate>Tue, 25 Aug 2026 03:49:12 +0000</pubDate><description>Georgiev and colleagues tested non-browser clients and libraries with adversarial certificate cases and found missing certificate-chain validation and hostname matching, with low-level interfaces, middleware, legacy dependencies and attempted fixes contributing to failures. Security engineers should test both checks throughout the software stack, but the sampled applications and study scope limit how broadly these findings can be applied.
A technical explanation of the paper's research question, method, reported findings and limitations. Across the affected client and library categories, the observed failures included missing certificate-chain validation and missing hostname matching. Some code deliberately disabled checks, while other code attempted custom verification but implemented it…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/34a9dcdb-6d84-426c-b5fa-3c79668c765c/66d4a2b4-9099-4113-bfdd-b1926740f86a.mp3" length="4277804" type="audio/mpeg"/><itunes:duration>267</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-most-dangerous-code-in-the-world-validating-ssl-certificates-i-58faef88/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">9778bdd7-9e2b-48fd-b066-6a7f83da1030</guid><title>A Look in the Mirror: Attacks on Package Managers</title><link>https://apimade.com/podcasts/research/a-look-in-the-mirror-attacks-on-package-managers-98ad44b8/</link><pubDate>Tue, 25 Aug 2026 03:48:32 +0000</pubDate><description>An examination of ten package managers in their 2008 configurations found each exposed to at least one malicious-mirror or network-intermediary attack, including replay of correctly signed old state, dependency metadata manipulation, or resource exhaustion from unbounded responses. Practitioners should authenticate repository metadata, compare repository versions, use signed expiration to detect indefinite freezes, and bound downloads, but these historical configurations do not establish how today’s package ecosystems behave.
A technical explanation of the paper's research question, method, reported findings and limitations. Every package manager examined had at least one malicious-mirror or man-in-the-middle attack in its evaluated configuration. Without enforced signatures, a mirror could substitute arbitrary packages. Package signatures did not protect unsigned dependency…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/693de3d7-73eb-44a1-a74f-db6993941900/114d813f-6aeb-4f7a-b266-8978cd14e416.mp3" length="4513964" type="audio/mpeg"/><itunes:duration>282</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/a-look-in-the-mirror-attacks-on-package-managers-98ad44b8/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">83904d21-dab4-4f12-a3f0-801b7387d269</guid><title>Spectre Attacks: Exploiting Speculative Execution</title><link>https://apimade.com/podcasts/research/spectre-attacks-exploiting-speculative-execution-76471d29/</link><pubDate>Tue, 25 Aug 2026 03:47:59 +0000</pubDate><description>Researchers showed that conditional-branch mistraining and indirect-branch target poisoning could encode secrets in cache state and expose memory in native programs and a Chrome browser process, where language and same-process sandbox checks were transiently bypassed. Conditional-branch behavior was observed on tested Intel and AMD processors, with initial ARM confirmation. Exploitability depends on CPU, software, compiler choices, and attacker interaction, while long-term solutions require processor changes.
A technical explanation of the paper's research question, method, reported findings and limitations. The native-code proof of concept located usable gadgets and read the victim process’s address space, including secrets. The JavaScript version read private memory inside its Chrome process, demonstrating that language checks and same-process sandbox checks…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/5ce8a1e9-a097-445c-b56e-f35e2eed9193/58ccc1d2-9c5a-4178-968c-639eabddc4aa.mp3" length="5882156" type="audio/mpeg"/><itunes:duration>368</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/spectre-attacks-exploiting-speculative-execution-76471d29/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">ef4bbc68-238f-4234-97c6-3d8255ce67d4</guid><title>Meltdown: Reading Kernel Memory from User Space</title><link>https://apimade.com/podcasts/research/meltdown-reading-kernel-memory-from-user-space-4bf440bd/</link><pubDate>Tue, 25 Aug 2026 03:47:25 +0000</pubDate><description>Lipp and colleagues showed that affected processors could transiently use supervisor-only bytes before rejecting a user-mode load, then recover those bytes through cache traces; page-table isolation blocked ordinary kernel and physical mappings in their tests. Defenders should preserve that isolation and scrutinize minimal mapped transition pages, while recognizing that the controlled cloud work did not establish cross-customer exploitation.
A technical explanation of the paper's research question, method, reported findings and limitations. The experiments demonstrated kernel or physical-memory disclosure on tested Linux and Windows systems. In a controlled Firefox case study, the researchers recovered saved-password material from physical memory. Controlled Docker, LXC, and OpenVZ tests also…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/b46428bc-3ee7-424b-98f3-8f650fa58d5f/48269908-98f0-43cc-bff0-a47a3db7c2a0.mp3" length="4445612" type="audio/mpeg"/><itunes:duration>278</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/meltdown-reading-kernel-memory-from-user-space-4bf440bd/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">158abe18-78ba-4e1d-b9bb-e57faa0b83ee</guid><title>CHERI: A Hybrid Capability-System Architecture for Scalable Software Compartmentalization</title><link>https://apimade.com/podcasts/research/cheri-a-hybrid-capability-system-architecture-for-scalable-softwar-e705e001/</link><pubDate>Tue, 25 Aug 2026 03:46:50 +0000</pubDate><description>Analysis of tcpdump covered 29 historical vulnerabilities, and the combined compartments addressed all but two. The cited evidence also reports cycle counts for function, libcheri, and process transitions, without establishing a comparative performance conclusion. Base CHERI does not natively provide temporal safety, while threat-model, trusted-code, and side-channel limitations also apply.
A technical explanation of the paper's research question, method, reported findings and limitations. In the tcpdump review, the combined compartments addressed nearly all of the 29 historical vulnerabilities examined. Another experiment measured per-sandbox processing cost as the prototype scaled to 128 sandboxes. The results support a limited conclusion:…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/90fdb9cb-f55d-4b35-8c65-23d1b50056ca/af10d4ae-f007-49e6-b0d6-404d1cd956a0.mp3" length="4261292" type="audio/mpeg"/><itunes:duration>266</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/cheri-a-hybrid-capability-system-architecture-for-scalable-softwar-e705e001/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">c93525a9-90ab-4b49-abdd-ce1b9256de78</guid><title>Flipping Bits in Memory Without Accessing Them: An Experimental Study of DRAM Disturbance Errors</title><link>https://apimade.com/podcasts/research/flipping-bits-in-memory-without-accessing-them-an-experimental-stu-a7d5d6d5/</link><pubDate>Tue, 25 Aug 2026 03:46:17 +0000</pubDate><description>Kim and colleagues showed that repeatedly activating and closing DDR3 memory rows could flip bits in other rows that software never touched, with errors appearing in over 80 percent of tested modules and chips. For security teams, this exposed a possible path to cross-process corruption, crashes or control hijacking, but the study did not build such an attack, and its PARA mitigation was simulated rather than implemented.
A technical explanation of the paper's research question, method, reported findings and limitations. Disturbance errors appeared in over 80 percent of the tested modules and chips. Many vulnerable cells flipped consistently when testing was repeated, which supports the conclusion that the behavior was reproducible rather than a collection of isolated random…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/0629ae59-49a2-4452-87fd-947ce71f9809/bf28c2c7-b654-4e40-987f-db3807e8e9fc.mp3" length="4889900" type="audio/mpeg"/><itunes:duration>306</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/flipping-bits-in-memory-without-accessing-them-an-experimental-stu-a7d5d6d5/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">ca25282e-a374-4868-b9c9-240ba0535276</guid><title>Modeling and Discovering Vulnerabilities with Code Property Graphs</title><link>https://apimade.com/podcasts/research/modeling-and-discovering-vulnerabilities-with-code-property-graphs-f2ee33b4/</link><pubDate>Tue, 25 Aug 2026 03:45:45 +0000</pubDate><description>Yamaguchi and colleagues combined source syntax, control flow, and program dependencies in a queryable code property graph, then used traversals to identify 18 previously unknown kernel vulnerabilities that developers addressed. Analysts can refine these traversals to balance false alarms against missed findings, but static analysis cannot cover runtime-dependent behavior, and this implementation analyzed within individual functions rather than across calls.
A technical explanation of the paper's research question, method, reported findings and limitations. Applied to the Linux kernel, the traversals identified 18 previously unknown vulnerabilities that developers addressed. The buffer-overflow case study returned 11 functions and seven vulnerabilities. The approach therefore surfaced actual flaws in the…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/73b467c6-09bd-401f-bceb-1886e5b18371/0419cf97-6733-404b-b3be-39ab0c34864c.mp3" length="3502124" type="audio/mpeg"/><itunes:duration>219</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/modeling-and-discovering-vulnerabilities-with-code-property-graphs-f2ee33b4/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">a8dac575-e031-4fd2-96e4-912bdca07cac</guid><title>seL4: Formal Verification of an OS Kernel</title><link>https://apimade.com/podcasts/research/sel4-formal-verification-of-an-os-kernel-26102403/</link><pubDate>Tue, 25 Aug 2026 03:45:12 +0000</pubDate><description>Klein and colleagues used Isabelle/HOL to prove that seL4’s C kernel implementation stayed within behavior allowed by an abstract specification and, within modeled assumptions, excluded crashes, null or misaligned pointer dereferences, assertion failures, and non-terminating kernel calls. Security architects can use that assurance to strengthen isolation, but the result did not verify compiler, assembly, hardware, boot and memory-management assumptions, multiprocessor concurrency, or timing-channel resistance.
A technical explanation of the paper's research question, method, reported findings and limitations. Within the modeled scope, the main theorem showed that the C implementation refined the abstract specification. Under its assumptions, the covered C paths could not crash or leave a kernel API call running forever. In those paths, pointer accesses had to be…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/0aeb868c-3605-4845-94b3-c2098445ce64/f3823344-74e2-4044-94e1-59152965049e.mp3" length="3989804" type="audio/mpeg"/><itunes:duration>249</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/sel4-formal-verification-of-an-os-kernel-26102403/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">fb85f429-5e81-4454-990c-7f8b6a886a5c</guid><title>The Geometry of Innocent Flesh on the Bone: Return-into-libc without Function Calls (on the x86)</title><link>https://apimade.com/podcasts/research/the-geometry-of-innocent-flesh-on-the-bone-return-into-libc-withou-4839ef4d/</link><pubDate>Tue, 25 Aug 2026 03:44:33 +0000</pubDate><description>Shacham showed that short, return-terminated instruction sequences already present in an x86 process could be chained into a manually built 12-word program that invoked execve on a shell path while write-xor-execute stayed active. Defenders should treat non-executable writable memory as incomplete protection against code reuse, while recognizing that the evaluation covered one older 32-bit Linux/glibc build and did not compare modern mitigations or exploit reliability.
A technical explanation of the paper's research question, method, reported findings and limitations. The chosen gadgets could move and transform data, steer execution and make system calls. By inspection, Shacham judged that set computationally complete. Shacham also built a 12-word return-oriented program that invoked execve on a shell path while…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/55b20bd3-8597-4ef0-b94e-553c65ff9458/60c16436-9cbf-4a36-8ae9-0b7d36222b09.mp3" length="4868396" type="audio/mpeg"/><itunes:duration>304</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-geometry-of-innocent-flesh-on-the-bone-return-into-libc-withou-4839ef4d/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">03d14902-ef8f-4218-9d7a-99970e8d49f8</guid><title>Automated Whitebox Fuzz Testing</title><link>https://apimade.com/podcasts/research/automated-whitebox-fuzz-testing-3a9d5588/</link><pubDate>Tue, 25 Aug 2026 03:44:00 +0000</pubDate><description>SAGE executes concrete inputs, records x86 binary traces, symbolically collects input-dependent path constraints, negates selected predicates and solves them to generate new inputs. The authors report more than 30 previously unknown bugs in shipped Windows applications; exploitability remained their assessment. Coverage was not a universal predictor of crashes, and SAGE’s incomplete heuristic exploration cannot prove that unexplored paths or bugs are absent.
A technical explanation of the paper's research question, method, reported findings and limitations. The authors reported that SAGE found more than 30 previously unknown bugs in shipped Windows applications. Some appeared potentially exploitable, but that judgment came from the authors rather than an independent assessment. For a compressed format, the…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/6b3fcb63-e0d2-4e5b-8e87-a9df9c3ff6a5/11976956-ca94-43ce-b95d-a6aad5755743.mp3" length="6005804" type="audio/mpeg"/><itunes:duration>375</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/automated-whitebox-fuzz-testing-3a9d5588/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">c5e65a10-f183-4d5e-ab55-11ff2083e8b2</guid><title>Guess Again (and Again and Again): Measuring Password Strength by Simulating Password-Cracking Algorithms</title><link>https://apimade.com/podcasts/research/guess-again-and-again-and-again-measuring-password-strength-by-sim-6f9b40a9/</link><pubDate>Tue, 25 Aug 2026 03:43:22 +0000</pubDate><description>Kelley and colleagues ranked 12,000 study passwords under 31 combinations of cracking algorithms and training data, finding that policy comparisons changed with the attack budget and that matched training data improved cracking against stronger-policy groups. Defenders can use attacker-aware rankings to compare policy choices, but the estimates are model-specific, one lookup stopped at 50 trillion guesses, and the study did not cover every attack type.
A technical explanation of the paper's research question, method, reported findings and limitations. The practical result is a budget-dependent reversal. Basic-sixteen eventually became more resistant than comprehensive-eight, although their ordering was opposite at lower guessing budgets. At the lower comparison point, the configured model also cracked far…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/1d619800-0b76-4cd2-977d-cd3a65860e1a/29174217-31b9-48f5-a8f2-73b8a58bfd16.mp3" length="5066540" type="audio/mpeg"/><itunes:duration>317</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/guess-again-and-again-and-again-measuring-password-strength-by-sim-6f9b40a9/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">2b8ea687-b961-41e6-827c-ab47ad7abbc5</guid><title>The Quest to Replace Passwords: A Framework for Comparative Evaluation of Web Authentication Schemes</title><link>https://apimade.com/podcasts/research/the-quest-to-replace-passwords-a-framework-for-comparative-evaluat-16262be6/</link><pubDate>Tue, 25 Aug 2026 03:42:50 +0000</pubDate><description>Bonneau and colleagues compared 35 web authentication schemes across usability, deployability and security, finding that none preserved every password benefit while improving on it. For identity teams, the framework supports lifecycle-level evaluation rather than choosing by login strength alone; its expert ratings were not controlled measurements. Coverage of mobile use, migration and business incentives was omitted or compressed, and complete recovery lifecycles were not evaluated.
A technical explanation of the paper's research question, method, reported findings and limitations. In the 2012 comparison of 35 schemes, none dominated passwords. No candidate delivered every usability benefit, and every alternative gave up at least one deployability benefit. Different families had different drawbacks. Hardware, paper and phone-based…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/8d490971-ec0f-4999-87a4-db432274499c/ca4536b8-861c-4aaa-acca-13e267230849.mp3" length="5715500" type="audio/mpeg"/><itunes:duration>357</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-quest-to-replace-passwords-a-framework-for-comparative-evaluat-16262be6/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">b1344696-dfe8-4a59-90fa-797a16b071b6</guid><title>So Long, And No Thanks for the Externalities: The Rational Rejection of Security Advice by Users</title><link>https://apimade.com/podcasts/research/so-long-and-no-thanks-for-the-externalities-the-rational-rejection-5db3f1d8/</link><pubDate>Tue, 25 Aug 2026 03:42:17 +0000</pubDate><description>Herley compares the user cost of password, URL-inspection and certificate-warning advice with the losses those behaviours might prevent, arguing that rejection can be rational when compliance costs exceed expected avoided harm. Security teams should measure harms, target at-risk users, prioritise and retire advice—but the URL estimate depends on victimisation, cleanup-time and wage assumptions, and the work does not encourage users to ignore policies or advice.
A technical explanation of the paper's research question, method, reported findings and limitations. For passwords, stronger-password advice can be irrelevant to phishing and keylogging attacks. Unique-password advice also increases burden under the analysis's reuse assumptions. Using a reported average reuse factor of 3.9 sites, Herley estimates that…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/760bb15c-bcd0-4bfb-8033-a5799e2407e6/643c7be6-6a49-4d54-a06f-316df5c2cea6.mp3" length="4208684" type="audio/mpeg"/><itunes:duration>263</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/so-long-and-no-thanks-for-the-externalities-the-rational-rejection-5db3f1d8/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">2ee8d29b-abb1-4b47-8baa-bb2dccdb4601</guid><title>Why Phishing Works</title><link>https://apimade.com/podcasts/research/why-phishing-works-12a69ff5/</link><pubDate>Tue, 25 Aug 2026 03:41:46 +0000</pubDate><description>In a 22-person study, the strongest replica fooled 20 participants, average error was about 40 percent, and passive browser security indicators plus a tested certificate warning often failed. Security teams should make untrusted states conspicuous rather than depend only on positive indicators, while recognizing that the small sample could not establish demographic or experience effects.
A technical explanation of the paper's research question, method, reported findings and limitations. The strongest replica fooled 20 of 22 participants, and average error was about 40 percent. Those measurements do not show that every lure works equally well; they show that at least one convincing imitation fooled nearly the entire sample. Passive SSL…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/ba195f59-2a39-4183-b4d6-a3b9e58f79f8/fbc2b169-097d-49b3-b87e-9aa69512a434.mp3" length="3600812" type="audio/mpeg"/><itunes:duration>225</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/why-phishing-works-12a69ff5/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">d07050b1-6d2c-400e-9631-fc4530012192</guid><title>Privacy in Pharmacogenetics: An End-to-End Case Study of Personalized Warfarin Dosing</title><link>https://apimade.com/podcasts/research/privacy-in-pharmacogenetics-an-end-to-end-case-study-of-personaliz-e7f84483/</link><pubDate>Tue, 25 Aug 2026 03:40:59 +0000</pubDate><description>Using black-box access to a warfarin dose model, patient-specific facts, and population priors, the researchers inferred VKORC1 genotype up to 22 percentage points above a 36 percent majority baseline. Health-model security teams should test leakage against realistic prior-based baselines and clinical harm, but not generalize this result: success depended on the model, auxiliary data, population assumptions, and a simulated rather than deployed clinical setting.
A technical explanation of the paper's research question, method, reported findings and limitations. For VKORC1, simply choosing the most common value was accurate roughly one-third of the time. With all evaluated background information, model inversion improved on that baseline by up to 22 percentage points, though it still trailed a separate linear…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/8c5e48d1-2fc1-41b7-a5b0-0f936500b9d4/3cd9fc38-15f8-49e2-ac23-a47b5ee1d3f6.mp3" length="5317292" type="audio/mpeg"/><itunes:duration>332</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/privacy-in-pharmacogenetics-an-end-to-end-case-study-of-personaliz-e7f84483/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">6dd3d636-8727-4831-bfbd-c4f6e6f402e7</guid><title>Granite: A Modular Methodology for Foundational Verification of Hardware-Software Leakage Contracts</title><link>https://apimade.com/podcasts/research/granite-a-modular-methodology-for-foundational-verification-of-har-91d43b9f/</link><pubDate>Sun, 23 Aug 2026 06:10:43 +0000</pubDate><description>Granite uses machine-checked proofs to connect an instruction-set leakage specification to cycle-by-cycle behavior in a synthesizable pipelined processor, then demonstrates integration with a proved static analysis for constant-time programming. The processor implementation is eliminated from the trusted computing base, but the evaluation uses a minimal single-hardware-thread RISC design and excludes power, within-cycle timing, and physical-access channels.
A technical explanation of the paper's research question, method, reported findings and limitations. Lau, Erbsen and Chlipala built a machine-checked correctness and confidentiality proof for synthesizable RTL implementing a pipelined processor. The design includes branch prediction and support for exceptions, interrupts and memory-mapped input and output.…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/9e2e03ac-9db9-46a1-bd45-c46639b43c64/d2d447f6-a1b7-4f8b-90db-1ecf85e74e97.mp3" length="6483500" type="audio/mpeg"/><itunes:duration>405</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/granite-a-modular-methodology-for-foundational-verification-of-har-91d43b9f/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">c07c11d2-4482-46a7-800f-fcd5112578c5</guid><title>Anomaly Detection using Knowledge Graphs: A Survey for Network Management and Cybersecurity Application</title><link>https://apimade.com/podcasts/research/anomaly-detection-using-knowledge-graphs-a-survey-for-network-mana-0eaa09e9/</link><pubDate>Sun, 23 Aug 2026 06:09:21 +0000</pubDate><description>The survey compares NMS and SIEM capabilities, semantic network models, and anomaly-detection techniques, finding that heterogeneous data hampers full contextualization of network and service failures. Security teams may use knowledge graphs to connect and reason over disparate telemetry, but should not expect complete automated incident context: current contextualization can omit network topology and operational information.
A technical explanation of the paper's research question, method, reported findings and limitations. The researchers found that established network-monitoring and security systems simplify analysis across assets, logs, alarms and vulnerability scans, but heterogeneous sources hinder full contextualization of failures. Semantic models for network and security…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/69a1855c-4bc0-44f6-a5e1-dd023ef24f86/71238dfc-8e10-47a1-9e2c-eb4b4ac6b954.mp3" length="5566892" type="audio/mpeg"/><itunes:duration>348</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/anomaly-detection-using-knowledge-graphs-a-survey-for-network-mana-0eaa09e9/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">7a12c3c2-603a-48f7-a6da-b76d08a9b25f</guid><title>The Bisq decentralised exchange: on the privacy cost of participation</title><link>https://apimade.com/podcasts/research/the-bisq-decentralised-exchange-on-the-privacy-cost-of-participati-4e711214/</link><pubDate>Sun, 23 Aug 2026 05:56:32 +0000</pubDate><description>Hickey and Harrigan built Bisq-specific address-clustering heuristics from Bitcoin transaction structure and Bisq peer-to-peer data, linking trading and governance activity across addresses and uncovering aliases that sometimes included real-world names. Bisq privacy engineers could offer optional dummy-transfer tooling and guidance, but it adds transaction cost, and possible false-positive alias links and deliberately induced false negatives limit confidence.
A technical explanation of the paper's research question, method, reported findings and limitations. The method aggregated multiple forms of activity under inferred participants, including trades, votes, and transfers. Hickey and Harrigan found cases where one cluster carried multiple aliases, including combinations of pseudonyms and real-world names. They…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/d0c9eada-6dd8-4664-9ab7-0ad37af4be14/a1027892-515b-4ca7-90bc-516963e1aefd.mp3" length="4857644" type="audio/mpeg"/><itunes:duration>304</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-bisq-decentralised-exchange-on-the-privacy-cost-of-participati-4e711214/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">fdf49080-5740-4b3c-868e-48e752669f20</guid><title>Evaluation and Hardening of LLM System Instructions Against Extraction via Encoding Attacks</title><link>https://apimade.com/podcasts/research/evaluation-and-hardening-of-llm-system-instructions-against-extrac-8827e023/</link><pubDate>Sun, 23 Aug 2026 05:50:10 +0000</pubDate><description>Sahu, Samanta and Soosahabi tested whether models that refused direct system-instruction requests would leak protected content when asked to encode or serialize it; structured formats produced the highest leakage rates, while small instruction rewrites reduced leakage. Security teams can add these transformations to pre-deployment tests and harden instruction wording, but the evaluation covered a limited model set and omitted possible multistage attacks.
A technical explanation of the paper's research question, method, reported findings and limitations. Structured wrappers, including configuration-like formats, consistently produced the highest leakage rates in the evaluated setting. Leakage also changed markedly between requests that meant essentially the same thing but used slightly different words or…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/71c9ff2f-8e40-45a3-a95a-5af7e63a39f2/fe26be4f-2df6-4ab6-b394-c174998d27dd.mp3" length="5318444" type="audio/mpeg"/><itunes:duration>332</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/evaluation-and-hardening-of-llm-system-instructions-against-extrac-8827e023/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">d9ed535f-4b74-49db-b1c3-e9e4d2093501</guid><title>AgenticRepair: Multi-Faceted Program Context Engineering for Agentic Vulnerability Repair</title><link>https://apimade.com/podcasts/research/agenticrepair-multi-faceted-program-context-engineering-for-agenti-3569ff27/</link><pubDate>Sun, 23 Aug 2026 05:44:54 +0000</pubDate><description>AgenticRepair combined code-structure, runtime-execution, and commit-history analysis with a dedicated repair agent, fixing 73% of 300 SEC-Bench cases and outperforming its strongest comparable baseline by 29%. The results support richer context and patch-integrity checks in repair workflows, but not autonomous deployment: the evaluation is limited to SEC-Bench, and generated patches still require functional review beyond sanitizer success.
A technical explanation of the paper's research question, method, reported findings and limitations. The full evaluation used 300 reconstructed SEC-Bench vulnerabilities drawn from 34 repositories, 32 projects, and 242 historical commits. Of these, 200 were Common Vulnerabilities and Exposures, or CVE, cases and 100 came from OSS-Fuzz. Each agent received an…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/f1c603fa-a081-4977-b39d-7635b6a7b901/f0bf869c-98ed-4a4f-ac36-88bdc84297fc.mp3" length="6971948" type="audio/mpeg"/><itunes:duration>436</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/agenticrepair-multi-faceted-program-context-engineering-for-agenti-3569ff27/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">8f56358e-4fc5-42ce-8376-711c08888bfd</guid><title>Cybersecurity laws, digital crimes, and ethical considerations: a multidimensional perspective on Cyber Risk Regulation (MPoCRR)</title><link>https://apimade.com/podcasts/research/cybersecurity-laws-digital-crimes-and-ethical-considerations-a-mul-2079332f/</link><pubDate>Sun, 23 Aug 2026 05:44:52 +0000</pubDate><description>Using secondary sources and structured qualitative matrices, researchers compared GDPR, HIPAA and NIS on legislative scope, enforcement and ethical sensitivity, concluding that existing regulation is fragmented and reactive to global, AI-enhanced threats. The proposed unified framework integrates data protection, AI ethics and legal compliance, but enforcement of extraterritorial rules such as GDPR is politically contested, and transplanted rules can fail without appropriate national implementation mechanisms.
A technical explanation of the paper's research question, method, reported findings and limitations. Within that qualitative comparison, definitions of cybercrime, enforcement procedures and the role of ethics varied across jurisdictions. The analysis characterizes U.S. regulation as more sector-specific, with less cohesive cross-border data governance and…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/3166ddb1-5e32-43a8-9818-91241d35db73/2f20245b-a435-4530-ba04-5c98a6f9f222.mp3" length="6044204" type="audio/mpeg"/><itunes:duration>378</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/cybersecurity-laws-digital-crimes-and-ethical-considerations-a-mul-2079332f/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">daf0ab04-e56a-48ee-9dac-714641ce2258</guid><title>Exploiting Cybersecurity Vulnerabilities for Financial Crime: An Integrated Framework for Understanding Fraudster Tactics, Digital Attack Pathways, and Financial Loss Prevention</title><link>https://apimade.com/podcasts/research/exploiting-cybersecurity-vulnerabilities-for-financial-crime-an-in-dd19c7c8/</link><pubDate>Sun, 23 Aug 2026 05:37:41 +0000</pubDate><description>The study builds an integrated framework linking technical vulnerabilities and fraudster tactics to attack paths, victim exposure, and financial-loss prevention, combining several cyber and financial analysis methods. Security and fraud teams can use that chain to coordinate intervention points, but publicly available datasets may miss emerging or institution-specific fraud patterns, limiting how well model findings carry across financial sectors.
A technical explanation of the paper's research question, method, reported findings and limitations. The framework introduces two related ways to express risk. The CEI, which stands for Cyber Exposure Index, assigns each vulnerability an importance weight and a measured severity score, then adds the weighted values. That makes more severe vulnerabilities…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/acc38949-a359-4eb8-af1a-e612612331aa/90156b70-c5bf-49f4-8f44-658b3feb2ff3.mp3" length="5298092" type="audio/mpeg"/><itunes:duration>331</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/exploiting-cybersecurity-vulnerabilities-for-financial-crime-an-in-dd19c7c8/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">66d1ea59-81d9-48d9-82c1-d9f0429162ac</guid><title>TopoIntent: Compiling Security Intent into Executable, Compliance-Checked Network Topologies</title><link>https://apimade.com/podcasts/research/topointent-compiling-security-intent-into-executable-compliance-ch-23a8454b/</link><pubDate>Sun, 23 Aug 2026 05:33:54 +0000</pubDate><description>TopoIntent converts natural-language business requirements into schema-constrained network topologies, checks topology-visible CIS safeguards, exports Mininet tests, and uses diagnostic feedback to improve policy enforcement; one feedback round raised the post-ACL pass rate from 0.78 to 0.88. This could help practitioners prototype zones, paths, and ACLs with executable checks, but it does not establish organizational CIS certification, and unresolved test endpoints require manual review.
A technical explanation of the paper's research question, method, reported findings and limitations. To determine what each component contributed, the researchers compared the full system with versions that disabled individual stages. Combining a retrieved reference design with the user’s intent improved coverage of required zone and device types over direct…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/812a4bc1-6770-4d73-8d02-a81da1ea5ecf/cdbf9ba4-5ae3-4f57-af20-a134fe5744a1.mp3" length="6039212" type="audio/mpeg"/><itunes:duration>377</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/topointent-compiling-security-intent-into-executable-compliance-ch-23a8454b/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">17b9176f-5021-4f5b-8a33-54bfe6a99099</guid><title>Small, Free, and Effective: Orchestrating Open-Weight Small Language Models to Outperform Single LLM for Malware Analysis</title><link>https://apimade.com/podcasts/research/small-free-and-effective-orchestrating-open-weight-small-language-3985ec41/</link><pubDate>Sun, 23 Aug 2026 05:30:06 +0000</pubDate><description>Researchers compared solo language models with four orchestration designs for structured questions about malware detonation reports. In the evaluated benchmark, a hybrid combining evidence retrieval with adversarial peer critique exceeded the strongest cyber-specialized and ungrounded frontier baselines, while grounded Gemini remained stronger. This could support locally deployed analyst assistance, but outputs require human verification; the study assessed multiple-choice report comprehension, not malware detection, low-level binary analysis, or open-ended operational triage.
A technical explanation of the paper's research question, method, reported findings and limitations. The open-weight hybrid slightly outscored the strongest frontier baseline used without retrieved evidence, but remained below Gemini when it was given the same evidence pipeline. The hybrid therefore narrowed the evidence-matched performance gap; it did not…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/f0b96b98-0327-4c1e-9b54-8e41f5dc8449/9c509208-b564-440e-8424-7f19bf2a278b.mp3" length="5159852" type="audio/mpeg"/><itunes:duration>322</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/small-free-and-effective-orchestrating-open-weight-small-language-3985ec41/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">8499382d-3d7a-4dfd-b235-6c53e5ceae1d</guid><title>Mapping CVEs to MITRE ATT&amp;CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion</title><link>https://apimade.com/podcasts/research/mapping-cves-to-mitre-attck-techniques-a-curated-gold-set-classifi-84d97822/</link><pubDate>Sun, 23 Aug 2026 05:26:17 +0000</pubDate><description>The researchers trained a multilabel classifier on expert-curated mappings that outperformed a semantic-similarity baseline across the evaluated ranking metrics. LLM-generated labels provided no reliable improvement and hurt rare-technique coverage at the largest tested expansion. Ranked outputs may help connect vulnerability feeds to detection, prioritisation and risk-assessment workflows, although the curated set is small and expert mappings may omit plausible techniques.
A technical explanation of the paper's research question, method, reported findings and limitations. The expert-trained classifier roughly doubled recall within the first 5 suggestions compared with the no-training similarity baseline, and every evaluated ranking metric improved. The label-expansion result was different: generated labels agreed with experts…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/f413d3dc-fa43-4ab7-9864-fd9227cc9369/c53d2485-7eac-4d26-8067-972b721b399d.mp3" length="6092972" type="audio/mpeg"/><itunes:duration>381</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/mapping-cves-to-mitre-attck-techniques-a-curated-gold-set-classifi-84d97822/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">818d273e-aea8-4399-b11d-105d7a01607b</guid><title>The Next Challenge for Agentic Cybersecurity: A Realistic, Contamination-Free Reverse Engineering Benchmark</title><link>https://apimade.com/podcasts/research/the-next-challenge-for-agentic-cybersecurity-a-realistic-contamina-71a7f871/</link><pubDate>Sun, 23 Aug 2026 01:10:39 +0000</pubDate><description>Researchers built SRE-Bench from private, real-world-scale programs with in-house anti-analysis primitives, then tested five frontier models in a standardized agent harness; even the strongest model fully recovered only a minority of binary instances. For practitioners, strong source-code performance is therefore poor evidence of readiness for malware, firmware, or proprietary-binary work, although the benchmark’s breadth is limited to 19 programs.
A technical explanation of the paper's research question, method, reported findings and limitations. The strongest model reached a 61.4% per-instance score but fully recovered only 31.5% of the instances. Applying the anti-analysis suite cut that model’s measured capability roughly in half and reduced every weaker model to near zero. Removing symbols was…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/ea6e2744-b740-4920-9e7a-87382e8b008d/343f3490-0159-4b36-86f8-011ee3a09c23.mp3" length="5000492" type="audio/mpeg"/><itunes:duration>312</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/the-next-challenge-for-agentic-cybersecurity-a-realistic-contamina-71a7f871/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">dd438f5c-e56b-4e14-9081-a31e9d2364b5</guid><title>Transforming Keystroke Noise to Text: Self-Supervised Acoustic Eavesdropping Attacks on Keyboards</title><link>https://apimade.com/podcasts/research/transforming-keystroke-noise-to-text-self-supervised-acoustic-eave-d1963629/</link><pubDate>Sun, 23 Aug 2026 01:06:13 +0000</pubDate><description>Okada and colleagues clustered unlabeled keystroke recordings, used Transformer-based language-model inference to resolve uncertain acoustic-to-character mappings, and achieved more than 99% reconstruction accuracy from 100–150 close-range keystrokes in their evaluated setup. Microphones may be leakage paths, but the online-meeting tests disabled noise suppression, which can attenuate keystroke sounds, and exact password recovery remained harder than natural-language reconstruction.
A technical explanation of the paper's research question, method, reported findings and limitations. In the close-proximity experiment, a smartphone near the target laptop captured enough audio for more than 99% reconstruction accuracy from 100–150 observed keystrokes. Okada and colleagues also evaluated multiple laptop platforms and several recording…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/9474723a-393e-4dd4-a8da-552ce060fc2a/1fcc4daf-8e10-4f93-820a-78d363458f4c.mp3" length="4590380" type="audio/mpeg"/><itunes:duration>287</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/transforming-keystroke-noise-to-text-self-supervised-acoustic-eave-d1963629/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">9de8120e-803a-4d2c-a915-6d2dfef377ce</guid><title>MaliciousSkillBench: A Comprehensive Benchmark for Malicious Agent Skill Detection</title><link>https://apimade.com/podcasts/research/maliciousskillbench-a-comprehensive-benchmark-for-malicious-agent-3527e4a7/</link><pubDate>Sat, 22 Aug 2026 06:56:20 +0000</pubDate><description>Researchers consolidated heterogeneous malicious-Skill sources, canonicalized and deduplicated records, separated structural reuse from attack semantics, and found that learned detectors degraded on held-out sources while scanners traded fewer benign false positives for lower malicious recall. For pre-installation screening, test cross-source performance and measure malicious detection alongside benign over-flagging; contributing datasets were built under different assumptions and should not be treated as interchangeable rows.
A technical explanation of the paper's research question, method, reported findings and limitations. Across the learned text models, Macro-F1 was higher with random splits but dropped when whole sources were held out. No evaluated detector combined high malicious recall with a low benign false-positive rate across those held-out sources. Differences in…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/ded0842e-efa1-4572-80c9-3ba30a5a6de7/5b7677e3-2b9a-49ed-a0f4-fa9cb3cc73d3.mp3" length="6135212" type="audio/mpeg"/><itunes:duration>383</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/maliciousskillbench-a-comprehensive-benchmark-for-malicious-agent-3527e4a7/transcript.txt" type="text/plain"/></item><item><guid isPermaLink="false">0eafc401-3141-4150-9508-59e815dd4d89</guid><title>QUASAR: A Quantum-Classical Neural Network for SAR Satellite Physical-Layer Authentication</title><link>https://apimade.com/podcasts/research/quasar-a-quantum-classical-neural-network-for-sar-satellite-physic-cbd71e81/</link><pubDate>Sat, 22 Aug 2026 05:37:12 +0000</pubDate><description>Sammartino, Denis and Di Pietro built a hybrid convolutional and variational-quantum classifier for X-band satellite fingerprints, evaluating 37 ICEYE satellites and attacks based on replay, crafted signals and space-borne spoofing. Ground-station defenders may gain a second authentication signal with less training data, but the 28-day, single-constellation evaluation and non-interchangeable learned fingerprints leave cross-system and long-term performance uncertain.
A technical explanation of the paper's research question, method, reported findings and limitations. QUASAR reached 97.3% validation accuracy, exceeding the classical-only baseline. It also matched classical baselines while using only a small fraction of the training data. For that reduced-data comparison, all baselines were trained on the same subset,…</description><enclosure url="https://research-podcast.securityveryseriously.com/assets/episodes/7d4fb389-1b2a-444c-b31b-f03c18862110/73fe2f60-3e85-4518-8445-19a3faf79722.mp3" length="4882220" type="audio/mpeg"/><itunes:duration>305</itunes:duration><podcast:transcript url="https://apimade.com/podcasts/research/quasar-a-quantum-classical-neural-network-for-sar-satellite-physic-cbd71e81/transcript.txt" type="text/plain"/></item></channel></rss>