Zach Riggle

Elaine is in Texas for a family emergency, so what do I do? Write a cryptography library in Rust. Here you go, fling mud if you find any issues: https://lnkd.in/gUY4VHRr

8

1 Comment

I've updated the page for the Encyclopedia of Crash Dump Analysis Patterns, Third Edition, adding all available purchase options https://lnkd.in/gckWeNxe

5

Security teams aren't under-skilled. They're outpaced. ORDR IQ applies AI where friction hits hardest: analysis, enforcement, and orchestration. One question replaces hours of coordination. Same team. Different scale.

9

Download Pentera Labs Report - revealing three new critical injection points in the ingress-nginx controller, building on Wiz’s IngressNightmare CVE. These overlooked vulnerabilities could let attackers hijack traffic, spoof headers, or reach unauthorized backend services - They exist in one of the most widely used ingress controllers in Kubernetes, putting countless environments at risk. This research highlights how small misconfigurations can lead to major exposure in modern cloud-native architectures. What’s Inside: ✅ 3 new injection vulnerabilities in ingress-nginx ✅ How attackers find and exploit CVEs in open source ✅ Actionable tips to secure your Kubernetes environment https://lnkd.in/eHtX6EdP

6

1 Comment

Here’s a pattern I’m seeing more often: More sites. More assessments. More reporting expectations. Same headcount. Security teams are being asked to scale output without scaling structure. So what happens? Assessments become episodic. Reporting takes too long. Prioritization becomes subjective. And leaders spend more time translating risk than reducing it. This isn’t a capability issue. It’s an architecture issue. At some point, physical security has to operate with the same operational discipline as finance and IT. Otherwise it stays in permanent catch-up mode. For security people overseeing medium to large portfolios (20+ sites): What’s currently your biggest bottleneck volume, visibility, or validation? And why do you think this is?

5

1 Comment

New GSA CUI rules caught you off guard? You’re not alone. With almost no announcement, GSA quietly updated its IT security procedural guide in January, rolling out new requirements for protecting Controlled Unclassified Information (CUI) in nonfederal systems. Any contractor handling CUI for GSA will be expected to follow this guide. Here’s the issue: cyber policy experts and industry advocates are already flagging key differences between these GSA requirements and DoD’s CMMC. For contractors working with both agencies, that misalignment could mean added complexity, cost, and compliance risk. If you’re a government or defense contractor, now is the time to: - Review how GSA’s CUI expectations differ from your current CMMC/NIST 800-171 posture - Identify gaps across policies, controls, and documentation - Plan for a unified compliance strategy that won’t slow down contract opportunities Need help assessing where you stand and how to streamline overlapping requirements? Idenhaus can support you with targeted cybersecurity and compliance assessments tailored for federal contractors. https://hubs.ly/Q046DgsK0

2

Tulsa International Airport Discloses Data Security Incident Some folks get their special someone chocolates and or flowers for Valentine's Day. They may even have a lovely dinner or a fun night out. Some unfortunate few got a breach notification 😕 On February 13, 2026, the Tulsa Airports Improvement Trust (TAIT) issued a public notice disclosing that an unauthorized third party accessed files from their systems between January 17–20, 2026. Exposed data may include a combination of the following PII: • Full names • Home addresses and phone numbers • Social Security numbers • Driver's license and government-issued ID numbers • Bank routing and financial account numbers Not all data elements were involved for every affected individual but details are still forthcoming. To their credit, TAIT responded quickly by moving to lock down their network, engaging a cybersecurity firm for forensic investigation, and notifying law enforcement. They are also enhancing existing controls, including layered technical defenses, employee training, MFA enforcement, and updates to their TSA-approved incident response plan. This incident is a good reminder that even organizations with established security programs can face sophisticated threats. Airports operate complex, multi-stakeholder IT environments, and incidents like this underscore why continuous improvement of detection and response capabilities matters across all sectors ESPECIALLY including critical infrastructure. #Cybersecurity #DataBreach #IncidentResponse #CriticalInfrastructure #Airport #InfoSec #IdentityTheft #SecurityOperations #PrivacyMatters #BlueTeam Notice of Data Security Incident - Fly Tulsa

1

Random reboots on Windows 11 in 2026 are getting blamed on graphics drivers. Often, that's the wrong call. CPU microcode updates pushed through BIOS/UEFI firmware are behind a lot of the stability complaints we're seeing right now. Manufacturers push these low-level processor instructions to patch security issues, but when they're not compatible with a specific hardware config, things get unpredictable fast. For IT teams, the pain is real: machines go down without warning, hardware gets misdiagnosed and replaced, and support tickets pile up chasing a problem nobody's named yet. The fix usually starts with auditing recent BIOS updates and checking microcode versions before assuming the hardware is shot. In some cases, rolling back to a previous firmware release is the right move. We wrote up the full diagnostic process on our blog if you want the step-by-step. #Windows11 #ITSupport #SysAdmin 🔗 https://lnkd.in/eXN7zjAm

1

1 Comment

What comes after Context Engineering and using a Spec Kit? The evolution so far: Prompt Engineering Context Engineering Forced Task Engineering (Spec Kit) And now... something I'm calling the Gang of 8. Here's how it works: We do research if necessary, then provide the agents with the problem and research. We spin up ~8 specialized agents — Architecture, Security, Compliance, Scaling, and others — running on Haiku 4.5. They debate the solution for 3 rounds. A Tech Lead on Opus 4.6 judges and picks the winners. Then a Devil's Advocate on Sonnet 4.6 challenges the output. Before coding starts, we load context from Context7. Then Claude Code does the work. If it's code, the Gang of 8 comes back for Code Review and bugs get fixed. The key: the 8 agents change depending on the task. Architecture reviews, websites, refactoring, security analysis — you name it. For simpler rework, a lite version with 3 agents handles it. Why? Because if you point AI at a problem, it comes at it with a mixed set of perspectives and it loses track of what is important. Like over engineering a solution or forgetting to add security. PS: This is backed by research, I did not invent or discover this. I did combine a number of approaches this week and found one that is working out well for me and others inside of Allianz. The debate cycle, devils advocate, and using multi-models are important in the testing I have done. What's your multi-agent workflow? Drop it in the comments — I want to see what others are building. #Allianz #ClaudeCode #GangOf8 #AIDebate

28

4 Comments

With less than a month remaining to submit for the Seattle Bsides Security Conference, I'm hosting another AMA focused on CFPs. Feel free to ask any questions you've had about CFP submissions in the comments below. In the meantime, here are some quick tips to enhance your submission: 1. Read all the directions carefully. 2. Avoid generic submissions; a one-sentence description for your abstract won't suffice. Provide enough detail to give reviewers a detailed understanding of your topic. 3. Include outlines and learning objectives to clarify your message. While optional, they can significantly strengthen your submission. 4. If examples are provided, review them, but remember that simply mimicking them does not guarantee acceptance. 5. Seek feedback and be prepared to iterate on your submission. Looking forward to your questions! #bsidesseattle #cfp #ama

68

1 Comment