惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Security Latest
Security Latest
Know Your Adversary
Know Your Adversary
S
Schneier on Security
K
Kaspersky official blog
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Google DeepMind News
Google DeepMind News
Project Zero
Project Zero
Recorded Future
Recorded Future
T
The Blog of Author Tim Ferriss
P
Palo Alto Networks Blog
Engineering at Meta
Engineering at Meta
MyScale Blog
MyScale Blog
L
LINUX DO - 热门话题
The Register - Security
The Register - Security
B
Blog
V
Vulnerabilities – Threatpost
M
MIT News - Artificial intelligence
P
Proofpoint News Feed
Cyberwarzone
Cyberwarzone
Latest news
Latest news
Webroot Blog
Webroot Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
美团技术团队
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
C
CXSECURITY Database RSS Feed - CXSecurity.com
L
LINUX DO - 最新话题
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
B
Blog RSS Feed
aimingoo的专栏
aimingoo的专栏
The GitHub Blog
The GitHub Blog
D
Docker
G
Google Developers Blog
T
Threatpost
F
Full Disclosure
Attack and Defense Labs
Attack and Defense Labs
L
Lohrmann on Cybersecurity
Application and Cybersecurity Blog
Application and Cybersecurity Blog
月光博客
月光博客
D
DataBreaches.Net
WordPress大学
WordPress大学
F
Fortinet All Blogs
S
Secure Thoughts
Y
Y Combinator Blog
博客园 - Franky
Scott Helme
Scott Helme
Apple Machine Learning Research
Apple Machine Learning Research
Hacker News: Ask HN
Hacker News: Ask HN
酷 壳 – CoolShell
酷 壳 – CoolShell
Cloudbric
Cloudbric
N
News | PayPal Newsroom

Sysdig Blog

Masterclass: AI is more than ChatGPT and LLMs CVE-2026-39987 update: How attackers weaponized marimo to deploy a blockchain botnet via HuggingFace Kubernetes 1.36 - New security features 5 steps to securing AI workloads Marimo OSS Python Notebook RCE: From Disclosure to Exploitation in Under 10 Hours Security briefing: March 2026 The Sysdig MCP server is now available in AWS Marketplace Risk isn’t reduced until you take action: How teams resolve issues in the cloud AI infrastructure security: Why it deserves its own category Three pillars for building effective runtime-powered cloud defense, the right way Closing the cloud security gap with runtime security Seeing risk isn’t stopping it: Why visibility alone isn’t enough TeamPCP expands: Supply chain compromise spreads from Trivy to Checkmarx GitHub Actions AI coding agents are running on your machines — Do you know what they're doing? Runtime security for AI coding agents: Protecting AI-assisted development How runtime insights power every cloud security use case CVE-2026-33017: How attackers compromised Langflow AI pipelines in 20 hours Inline Cloud Response: Accelerating AWS threat containment for SOC teams Runtime malware detection for AWS Fargate Detecting CVE-2026-3288 & CVE-2026-24512: Ingress-nginx configuration injection vulnerabilities for Kubernetes Malware detection with Sysdig Security briefing: February 2026 Leveling up Kubernetes Posture: From baselines to risk-aware admission Eliminating runtime blind spots: How CleanStart and Sysdig build continuous trust across the container lifecycle LLMjacking: From Emerging Threat to Black Market Reality Real risks live at runtime: Why CISOs must care about deep telemetry in 2026 Sysdig named a Leader in the Forrester Wave™: Cloud Native Application Protection Solutions, Q1 2026 How to run rootless containers AI-assisted cloud intrusion achieves admin access in 8 minutes Security briefing: January 2026 Securing GPU-accelerated AI workloads in Oracle Kubernetes Engine Bringing OSS runtime security to AWS: Falco integration with AWS Security Hub CSPM Our customers have spoken: Sysdig rated a Strong Performer in Gartner® Voice of the Customer for Cloud-Native Application Protection Platforms Protecting sensitive business data in preparation for the organization's Gen AI VoidLink threat analysis: Sysdig discovers C2-compiled kernel rootkits AI is still a workload: A practical guide to securing AI workloads How threat actors are using self-hosted GitHub Actions runners as backdoors How Sysdig Sage delivers AI-powered, real-world vulnerability management Security briefing: December 2025 Top 10 ways to get breached in 2026 EtherRAT dissected: How a React2Shell implant delivers 5 payloads through blockchain C2 Introducing runtime file integrity monitoring and response with Sysdig FIM How to detect multi-stage attacks with runtime behavioral analytics EtherRAT: DPRK uses novel Ethereum implant in React2Shell attacks Detecting React2Shell: The maximum-severity RCE vulnerability affecting React Server Components and Next.js The rise of AI agents: How autonomous AI Is transforming cloud security Kubernetes 1.35 - New security features The Urgency of Securing AI Workloads for CISOs Security briefing: November 2025 Quantum and the cloud: Science fiction turned security strategy Cloud security, the right way: What the industry should demand (and why "good enough" isn't) Return of the Shai-Hulud worm affects over 25,000 GitHub repositories Detecting CVE-2024-1086: The decade-old Linux kernel vulnerability that’s being actively exploited in ransomware campaigns What’s old is new again: How to demystify AI security with AIBOMs Securing Kubernetes with agentic cloud security How agentic cloud security reduces real risks Hunting reverse shells: How the Sysdig Threat Research Team builds smarter detection rules Shifting left with AI and MCP: Sysdig + Amazon Q Developer How Falco and Stratoshark close the gap between open source runtime detection and deep forensic analysis Investigating security issues with ChatGPT and the GitHub MCP server New runc vulnerabilities allow container escape: CVE-2025-31133, CVE-2025-52565, CVE-2025-52881 Harden your LLM security with OWASP Security briefing: October 2025 How agentic AI is changing cloud security Kubernetes Incident Response: Detect, investigate, and contain in under 10 minutes Sysdig recognized as a Cloud Security Leader in Latio Tech Cloud Security Market Report AI echolocation of cloud risks using Sysdig & Snyk MCP servers Sysdig MCP Server: Bridging AI and cloud security insights Understanding CVE-2025-49844: “RediShell” Critical Remote Code Execution in Redis How Sysdig secures your containers and Kubernetes Sysdig Security Briefing: September 2025 Cloud security, the right way: The 3 pillars of real-time defense Open source spotlight: Bringing web application security to Falco with Falcoya's Nginx plugin Malicious NPM packages: Are you exposed? AI for SOC teams: 5 cloud security prompts to start your day with Sysdig Sage™ Shai-Hulud: The novel self-replicating worm infecting hundreds of NPM packages ZynorRAT technical analysis: Reverse engineering a novel, Turkish Go-based RAT Modern vulnerability management, built for the cloud Build your AWS incident response playbook with open source tools 2025 Gartner® CNAPP Market Guide: Runtime visibility is no longer optional Threat hunting with Sysdig: Uncovering “IngressNightmare” Open source spotlight: From alerts to action with AI-powered Falco Vanguard From triage to action: How Sysdig’s agentic cloud security platform slashes noise and accelerates remediation The vision comes to life: Agentic cloud security with Sysdig Sage™ Connecting runtime to source: Sysdig and Semgrep integration Fix what matters, faster: How Sysdig and Semgrep are unifying security without silos – from code to runtime Defending sensitive data with Sysdig Secure Redefining cloud security, the right way Join the movement: The Sysdig Open Source Community is live A smarter, safer cloud in the age of AI Unifying detection and response: Sysdig + Cortex XSOAR for security at cloud speed The future of security is open, and it needs a unified hub: The Sysdig Open Source Community is here CVE-2025-53104: Command injection via GitHub Actions workflow in gluestack-ui Why MCP server security is critical for AI-driven enterprises What’s new in Sysdig — June 2025 AI-powered CNAPP with Sysdig Sage™ Revolutionizing Cybersecurity Search with Sysdig Sage™ Sysdig Threat Bulletin: Iranian Cyber Threats The end of the prioritization-only era: Vulnerability management needs action Dangerous by default: Insecure GitHub Actions found in MITRE, Splunk, and other open source repositories
Data security findings: A technical deep dive
2025-07-31 · via Sysdig Blog

We recently shared a high-level look at our new Sysdig Secure data security findings feature, highlighting how it helps security leaders reveal data exposure and contextualize threats. That post covered the “what” and “why” of the feature. In this post, we’ll take a closer look at the “how.”

Building deep data security without adding overhead

Delivering meaningful data security insights often comes at the cost of additional tools, agents, or operational complexity. We wanted to avoid that trap. Rather than requiring customers to deploy a separate, standalone scanning product that introduces new agents or moves sensitive data out of their cloud environment for analysis, we've extended the power of the Sysdig Secure platform with sensitive data discovery, powered by an integration with Bedrock Security. This approach treats data as a first-class security signal, alongside vulnerabilities, misconfigurations, and runtime events. This creates a unified model of risk that practitioners can use to prioritize and remediate with confidence.

The technical challenge: From data to findings

In our previous post announcing data security findings, we touched on the challenge of data sprawl. For engineers, this is more than a buzzword: It’s a persistent technical challenge. Cloud storage is often unstructured, constantly changing, and distributed across multiple services. Traditional scanning solutions can be slow and resource-intensive, and require exfiltrating data to a separate system for analysis. That not only increases cost but also introduces additional security and compliance risks.

To solve this, we’re using a scanning mechanism that operates in place, directly within the customer’s cloud environment. By partnering with Bedrock Security, we leverage AI-powered classification and detection to analyze data where it lives — for example, in S3 buckets — without moving sensitive content outside of the account. Only classification results and metadata are returned to Sysdig, where they are ingested as structured findings and correlated with other elements of your cloud security posture.

This serverless architecture, powered by Adaptive Sampling, efficiently scales to analyze massive and constantly changing datasets. It’s cost-effective, accurate, and avoids the pitfalls of lift-and-shift data analysis. Most importantly, it keeps sensitive data in place while enriching the Sysdig risk model with data-driven intelligence.

How it works

Understanding the architecture behind new capabilities is key for practitioners. We've designed Sysdig data security findings to operate with minimal friction and maximum security by keeping sensitive data in place while enhancing visibility and risk context across your cloud security environment. The diagram below illustrates the high-level flow, from data discovery within your cloud environment to actionable insights in the Sysdig Secure Platform.

As the diagram shows, the process begins directly within your cloud, leveraging serverless technology to efficiently scan and classify sensitive data without requiring new agents. Only classification results and metadata are generated by the in-environment outpost analyzer and then transmitted to the Bedrock SaaS Platform for further processing before being securely sent as structured findings to the Sysdig Secure platform. This "metadata only" approach is a critical design choice, ensuring sensitive information never leaves your environment. Once integrated into Sysdig Secure, these findings immediately enrich your existing cloud security posture, enabling powerful new use cases that we'll explore next.

Integrating data into the graph

The real value of data security findings lies in how they connect to Sysdig’s broader context. A single data finding may indicate a risk, but combining it with other signals, like a misconfiguration or anomalous runtime activity, turns it into an actionable, prioritized security event. This directly addresses the problem of security teams lacking context to effectively prioritize risk or enforce policies for business-critical data.

Enriching the Risk Engine

Attack paths in Sysdig Secure map potential attack paths across assets, configurations, and identities. With data security findings, sensitive data is now a critical node in this graph. This provides crucial information to help apply the right security controls and prioritize fixes that reduce the most risk. For example, if a publicly accessible S3 bucket contains PII, the graph can now highlight a direct path from a misconfiguration to sensitive data exposure.

Actionable SysQL Queries

For teams that prefer automation or need custom alerts, all data findings are fully queryable via SysQL. This enables rapid identification of high-risk resources without the need to manually correlate findings across tools.

By querying for sensitive data in exposed or misconfigured environments, security teams can quickly elevate the threats that matter most, accelerating triage and policy enforcement. This aligns with Data Detection and Response (DDR) principles and allows risks in Sysdig Secure to be precisely tailored to your business priorities.

For example, to find exposed cloud resources containing credit card data in a staging environment, you could run:

MATCH CloudResource IN Zone
WHERE CloudResource.isExposed = true AND Zone.name IN ['pci-dev']  

MATCH CloudResource CONTAINS SensitiveData
WHERE SensitiveData.dataClass IN ['Credit Card PAN']
 RETURN DISTINCT CloudResource, Zone, SensitiveData
LIMIT 50;

Or if you’re concerned about AI-related workloads with access to sensitive data (for example because of training concerns or potential leaks via retrieval-augmented generation) you could try:

MATCH EC2Instance PACKAGE_INSTALLED_ON Package OVER RuntimeMetadata
WHERE Package.isAI = true
MATCH EC2Instance ASSOCIATED_WITH IAMInstanceProfile CONTAINS IAMRole HAS_ACCESS S3Bucket CONTAINS AS CONTAINS2 SensitiveData
RETURN DISTINCT EC2Instance, Package, IAMInstanceProfile, IAMRole, S3Bucket, SensitiveData
LIMIT 50;

A Unified User Experience

Data security findings integrate directly into the Sysdig Secure UI. Resource detail views now include a dedicated data findings section, alongside existing context like vulnerabilities, misconfigurations, and other findings. Teams can see everything they need in one place without breaking out of workflows, leading to faster, more confident decisions during incident response.

Making CNAPP more context-aware

Data security findings don’t just add another signal; they strengthen the overall intelligence of our CNAPP platform. By connecting the where (cloud resources), the how (runtime activity and vulnerabilities), and now the what (sensitive data), Sysdig Secure provides a more accurate view of business risk and helps satisfy several key compliance requirements.

Our goal is to reduce noise, highlight the issues that matter most, and help teams protect sensitive data with better speed and confidence. This continuous feedback loop directly supports reducing Mean Time to Remediate (MTTR) for risks with sensitive data findings. We encourage you to explore this new capability and connect with your account team to enable data discovery in your environment.

Want to see Sysdig Secure in action? Request a demo today!