Gokhan Ozhan

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

Existing IAM concepts for agent identity and auth? Are you serious? Autonomous agents work with probabilistic intent and outcomes, shift roles rapidly, cross org boundaries, may exist ephemerally for a single task, but operate at machine speeds and scale. Your existing identity infrastructure was built for humans or machines, not agents that spawn, collaborate, and disappear in seconds. We built an Agent Identity Service powered by AGNTCY | A Linux Foundation Project that delivers: 🫆Cryptographic badge generation for MCP Servers and AI Agents using A2A / MCP / OASF specs 🫆Human-in-the-loop policy authorization for critical actions with real-time mobile approvals 🫆Native integrations with Duo Security, Okta, Ory Corp, plus AGNTCY's DID-based identity provider Tamper-proof badges that prove identity and capabilities. Plugs into whatever identity infrastructure you already run. Free SaaS built on a Linux Foundation project because agent identity standards cannot be vendor-controlled. Code on GitHub. We created a currency exchange demo showing the complete workflow. Financial assistant authenticates with exchange agent, both verify cryptographic badges, human approval required for transfers. Every action traceable to specific agent identity. No more wondering which agent transferred money or called that API. No more forensic investigations when something breaks. Read the blog by Julu Panat & Hervé Muyal for details https://lnkd.in/g_MnVuQ7 Try it. Tell me what works, what doesn't.

148

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

The Cybersecurity and Infrastructure Security Agency (CISA), along with the FBI, Department of Defense Cyber Crime Center, and National Security Agency, has issued an urgent warning regarding potential cyber attacks by Iranian-affiliated actors targeting U.S. critical infrastructure. Despite ongoing ceasefire negotiations and diplomatic efforts, these threat actors continue to pose significant risks to American networks and systems, particularly those within the Defense Industrial Base sector. Stay connected to Anuj Arora for content related to Cybersecurity.   #LinkedIn #Cybersecurity #Cloudsecurity #AWS #GoogleCloud #Trends #informationprotection #Cyberthreats #CEH #ethicalhacker #hacking #cloudsecurity #productmanagement #cybersecurity #appsec #devsecops #Cloudstrategy #cloudgovernance #ITIL #Azure #Datasecurity      https://lnkd.in/g7uavW2d                                                                                                         

1

For SOCs, it’s not just the hackers that pose a threat - it’s the avalanche of data that buries real signals under noise. Security logs, once the fuel for detection, are now both an asset and a liability. The flood of redundant, misaligned, or uncurated telemetry drains not just budgets - but analysts. The challenge isn’t just collecting data - it’s collecting the right data, in the right shape, at the right time. Security tools generate logs by the terabyte. Yet most organizations lack a strategy to qualify, contextualize, or prioritize what enters their SIEMs. As a result: ▪ Real threats get buried in noise. ▪ False positives clutter dashboards, wasting attention. ▪ Costs balloon from excessive licensing and storage. To move from reactive firefighting to proactive defense, SOCs must elevate telemetry management as a core security function. Here's how leading teams do it: 1. Precision Filtering, Not Blanket Collection Start with a threat-informed view: what data truly supports detections? Eliminate noise - e.g., suppress successful login logs unless from unusual geographies or times. 2. Normalization and Enrichment as Multipliers Standardize formats and enrich with business context - asset criticality, user identity, threat intel, geolocation. This transforms raw logs into events that trigger rules more accurately and reduce triage ambiguity. 3. Retention That Reflects Risk Abandon “store everything” habits. Align retention with risk: real-time detection data stays hot; compliance data can go cold. 4. Use Case-Driven Collection Let strategy guide ingestion. Data should map to real correlation rules, MITRE ATT&CK coverage, or compliance needs. If it doesn’t, reconsider ingesting it. Log optimization isn’t just about saving money, it enables: ▪ Faster decision-making ▪ Reduced alert fatigue ▪ Stronger detection fidelity When telemetry pipelines are treated with the same rigor as detection logic or incident response, the SOC becomes sharper and more effective. Final thought…. Data isn't your greatest asset - useful data is. 👉Ask Yourself Are you collecting data to feel secure - or to be secure? #CyberSecurity #SOC #SecOps #ThreatDetection #Telemetry #DataStrategy #DataQuality #OptimizeLogs #LogReduction #SecurityEfficiency #SIEMOptimization #AlertFatigue #TelemetryPipeline

33

4 Comments

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

SOTA agent frameworks rely on probabilistic "vibes" and lack deterministic User-to-Agent Authorization mapped to data classification. This makes them mission-unsuitable for military use, where multi-level security requires microsecond, pre-computed gating instead of slow, bypassable LLM reasoning...

This proposal signals a fundamental recalibration of how the United States balances security, privacy, and openness. If implemented, it could reshape global travel norms, strain diplomatic relationships, and redefine expectations for digital privacy at borders just as the U.S. prepares to host one of the world’s largest sporting events.

1