Ian Hellen

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

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

Tackling DNS abuse requires targeted, proportional, and collaborative solutions. The latest policy blueprint by the NetBeacon Institute outlines concrete actions—such as limiting high-volume domain registrations for new accounts, addressing subdomain abuse, and improving coordination on DGA-based threats. These proposals reflect the kind of pragmatic, community-led thinking our industry needs to strengthen DNS trust and integrity. As part of the .CO SecOps team, I remain fully committed to advancing security, accountability, and responsible governance across the global domain name ecosystem. #DNSAbuse #InternetGovernance #DomainSecurity #NetBeacon #COInternet #TrustAndSafety #CyberPolicy

3

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

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

IMO, Trusted Publishing (along with provenance attestations) has been the single-best advancement for securing public package repositories. Firstly, it rids the need for long-lived tokens, which I can hope we all agree suck. But also, most people didn't realize that until recently (and still today with certain registries), nothing has tied source code repositories to the artifact published. Yes, you could publish a package you created, and link the source repository of any project, instead of your own 🙃. With Trusted Publishing, authentication is performed by exchanging OIDC identity tokens for short-lived and tightly scoped API tokens to authenticate with package repository publishing APIs. Provenance attestation similarly leverages OIDC, so it makes sense to use them in unison. During a workflow, you can build an artifact, attest to its origins, and publish to a package registry all at once. Enabling the registry to verify the origins of the published artifact.

51

6 Comments

Regarding the recent Anthropic marketing post in which they claim their LLM has identified 500 high-severity vulnerabilities, I'd like to make you aware of the following exchange on oss-security: https://lnkd.in/dn5nKdRn

261

33 Comments