Adam Bacchus

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

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

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

🔐 𝗧𝗛𝗘 𝗙𝗨𝗧𝗨𝗥𝗘 𝗢𝗙 𝗦𝗘𝗖𝗨𝗥𝗜𝗧𝗬 𝗢𝗣𝗘𝗥𝗔𝗧𝗜𝗢𝗡𝗦 𝗜𝗦 𝗛𝗘𝗥𝗘 Traditional SOCs are drowning in noise. 🔺Manual alert triage 🔺Slow response times 🔺Siloed tools 🔺Reactive firefighting 🔺High false positives 🔺Analyst burnout 𝗧𝗵𝗶𝘀 𝗶𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗶𝗻𝗲𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁 — 𝗶𝘁’𝘀 𝗿𝗶𝘀𝗸𝘆. 🚀𝗪𝗘𝗟𝗖𝗢𝗠𝗘 𝗧𝗢 𝗧𝗛𝗘 𝗔𝗜-𝗣𝗢𝗪𝗘𝗥𝗘𝗗 𝗦𝗢𝗖 𝗘𝗥𝗔 Modern Security Operations Centers are shifting from reactive to proactive with AI-driven automation and real-time threat intelligence. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝘀? ✅ Alerts are triaged automatically ✅ Threats are detected and analyzed in real time ✅ Data is correlated across a unified platform ✅ Hidden threats are hunted proactively ✅ False positives are drastically reduced ✅ Analysts focus on what truly matters 𝗧𝗛𝗘 𝗢𝗨𝗧𝗖𝗢𝗠𝗘? 𝗙𝗮𝘀𝘁𝗲𝗿 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀. 𝗦𝗺𝗮𝗿𝘁𝗲𝗿 𝗱𝗲𝗳𝗲𝗻𝘀𝗲. 𝗦𝘁𝗿𝗼𝗻𝗴𝗲𝗿 𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗽𝗼𝘀𝘁𝘂𝗿𝗲. Security operations shouldn’t fight noise. They should be powered by intelligence. 𝗧𝗛𝗘 𝗙𝗨𝗧𝗨𝗥𝗘 𝗢𝗙 𝗦𝗢𝗖 𝗜𝗦 𝗔𝗨𝗧𝗢𝗠𝗔𝗧𝗘𝗗, 𝗨𝗡𝗜𝗙𝗜𝗘𝗗, 𝗔𝗡𝗗 𝗣𝗥𝗢𝗔𝗖𝗧𝗜𝗩𝗘. #CyberSecurity #SOC #AISecurity #XDR #ThreatIntelligence #DigitalDefense #SecurityOperations #FutureOfSecurity Sujit Kumar AMAL N R Nilesh Mojidra Yashesh Vaishnav Alina Prem Mohamed Adil Rajesh P Raveendran. Seceon Inc. Arrownex

18

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