< ciso
brief />
Tag Banner

All news with #aws security hub tag

54 articles

How AWS Security Incident Response Triages Your Findings

πŸ›‘οΈ AWS Security Incident Response continuously triages threat findings from Amazon GuardDuty and AWS Security Hub CSPM, yet most of that work never surfaces as a case. A new AWS post explains what happens to each finding, from ingestion to archiving or escalation. It also shows how to verify triage through the Proactive response dashboard and the monthly report. Across customers, fewer than 1 percent of findings result in an escalation.
read more β†’

AWS Security Hub adds resource criticality signals

πŸ”’ AWS Security Hub now uses installed software and resource usage as additional signals to infer resource criticality, helping prioritize exposure findings. Previously, Security Hub relied on tags and names, which left many resources with Unknown criticality. The new signals assign more meaningful criticality without extra tagging or configuration, and are available in the Security Hub Essentials plan at no extra cost.
read more β†’

AWS Security Hub Adds Native Monitoring for GCP

πŸ”’ AWS Security Hub now monitors Google Cloud Platform resources, extending CSPM, vulnerability management, and response capabilities across AWS and GCP. It automatically discovers GCP VMs, Artifact Registry images, Cloud Run functions, and identities, evaluating them for misconfigurations, internet exposure, and vulnerabilities. Findings from AWS and GCP appear in a unified prioritized view with consistent formats and EventBridge automation, and a 30-day free trial for GCP monitoring is available.
read more β†’

Security Hub flags EC2 instances running vulnerable software

πŸ” AWS Security Hub now identifies when software with a known vulnerability is actively running on Amazon EC2 instances. Exposure findings include a new trait, The EC2 instance is running software with a known vulnerability, and receive higher severity when the software is in use. The capability correlates data from Amazon GuardDuty Runtime Monitoring and Amazon Inspector VM Scanner to prioritize runtime risk and streamline remediation. It is available at no extra cost with the Security Hub Essentials plan in supported Regions.
read more β†’

Security Hub adds RDS network scanning capability

πŸ” AWS Security Hub's Network Scanning now discovers and scans Amazon RDS DB instances configured for public access, creating findings for each reachable port. The feature automatically detects existing and new RDS instances in accounts and generates detailed findings that include instance and port information. Enabled automatically for customers with Network Scanning turned on, RDS scanning enhances visibility into internet-reachable resources and is included with Security Hub Essentials at no extra cost in supported Regions.
read more β†’

Security Hub CSPM supports AWS Organizations policies

πŸ”’ AWS Security Hub CSPM now supports declarative AWS Organizations policies to enable and manage CSPM across all accounts and Regions. Policies can be applied broadly or targeted to specific account-and-Region combinations, and they can be auto-applied to new accounts to prevent configuration drift. Declarative policies are the recommended method and align management with other AWS security services; a migration tool converts central configuration into declarative policies.
read more β†’

AWS Security Hub adds organization-wide SBOM inventory

πŸ”’ AWS Security Hub now provides a centralized Software Bill of Materials (SBOM) inventory that gives security teams a continuously updated view of packages and applications across compute resources. The inventory is built from SBOMs Amazon Inspector generates for EC2 instances, ECR images, and Lambda functions, and it lists packages with version, type, and resource counts. Users can filter and group results, view per-resource Installed software, and query via the Security Hub API. The feature is included with Security Hub Essentials, requires no additional enablement, and is available in all Regions where Security Hub is offered.
read more β†’

AWS Security Hub Network Scanning Now in GovCloud

πŸ” AWS Security Hub Network Scanning is now available in AWS GovCloud (US). The feature probes resources from the internet to detect actual reachability, discovering public IPs, VMs, and load balancers, identifying open ports and running services. Findings for each reachable port are created in Security Hub and correlated by Security Hub Exposures to assess broader risk. Network Scanning can be enabled per account or organization-wide and is included with Security Hub Essentials at no extra cost.
read more β†’

Amazon Inspector Adds AMI Vulnerability Scanning

πŸ” Amazon Inspector now scans EC2 AMIs for software vulnerabilities without requiring instance launches or extra agents. You can run continuous evaluations or targeted one-time scans from the EC2 Console and enable AMI scanning account-wide or organization-wide. Findings can be forwarded to AWS Security Hub, integrated into EC2 Image Builder pipelines, and used with Allowed AMIs and Declarative Policies to enforce security criteria.
read more β†’

AWS Security Hub adds CRI Profile v2.2 checks

πŸ”’ AWS Security Hub CSPM now includes automated checks mapped to the Cyber Risk Institute (CRI) Profile v2.2, providing 404 controls that cover a subset of CRI requirements. The controls are available in all Regions where Security Hub CSPM is offered, including AWS GovCloud (US) and China Regions. Use Security Hub central configuration to enable the new standard across multiple accounts and Regions with a single action, noting that requirements needing manual verification are not included.
read more β†’

AWS Security Hub adds resource criticality support

πŸ”’ AWS Security Hub now adds resource criticality to exposure prioritization so central security teams can focus on exposures affecting their most business-critical assets. You can define criticality with automation rules (for example, mark compute resources as Very High), and the rules apply to existing and newly discovered resources. Security Hub also infers criticality from resource tags and names, records the source of the determination, and displays criticality on the Resources page and Impact assessment tab. This capability is included with Security Hub Essentials at no extra cost and is enabled for all customers.
read more β†’

GuardDuty adds five indicators to improve detections

πŸ”’ Amazon GuardDuty Extended Threat Detection now attaches five new indicator types β€” MALICIOUS_PACKAGE, MISCONFIGURATION, REACHABILITY, SENSITIVE_DATA, and VULNERABILITY β€” to correlated attack-sequence findings. These indicators are sourced from Amazon Inspector, Amazon VPC Reachability Analyzer, Amazon Macie, and AWS Security Hub, and appear in the Indicators tab and GetFindings JSON. The added context helps promote weak runtime signals into higher-confidence CRITICAL findings for Amazon EC2, ECS, and EKS workloads, improving prioritization and reducing noise.
read more β†’

AWS Security Hub adds S3 CSV and JSON exports

πŸ“ AWS Security Hub now supports exporting findings directly to Amazon S3 in either CSV or JSON (OCSF) formats. This feature lets security teams export from any findings page β€” including Threats, Exposure, Vulnerabilities, Posture Management, Sensitive Data, and All Findings β€” without building custom extraction pipelines. Exports can be started on demand and delivered to an S3 bucket in your account. The JSON option aligns with the Open Cybersecurity Schema Framework (OCSF).
read more β†’

AWS Security Hub Adds GuardDuty Runtime Monitoring

πŸ”” AWS has integrated Amazon GuardDuty Runtime Monitoring into the AWS Security Hub Threat Analytics plan. This runtime capability inspects OS, network, and file activity to detect threats like container escapes, privilege escalation, and cryptomining across Amazon EC2, Amazon EKS, and Amazon ECS on AWS Fargate. Billing for Runtime Monitoring is now consolidated under Security Hub as a single usage type, eliminating separate GuardDuty Runtime Monitoring charges for accounts and regions with Security Hub enabled. Detection behavior, finding types, and GuardDuty agents remain unchanged, and no reconfiguration is required; free-trial terms for Threat Analytics and Security Hub Essentials remain separate.
read more β†’

AWS Security Hub adds remediation plans to prioritize fixes

πŸ”’ AWS Security Hub now groups related exposure findings into remediation plans that target shared root causes. Each plan provides prioritization (Critical, High, Medium, Low), impact assessment, and step-by-step remediation instructions with examples for AWS CLI, Terraform, CloudFormation, Python, and CDK. Security Hub automatically ranks plans by potential risk reduction so teams can focus on the most impactful fixes, and AI agents can consume the plans via API to automate remediation. Remediation plans are available in all Regions where Security Hub is offered and included at no extra cost under the AWS Security Hub Essentials plan.
read more β†’

Security Hub AI Inventory Adds Azure Self‑Hosted Support

πŸ” AWS Security Hub AI Inventory now discovers and catalogs AI assets on self‑hosted Microsoft Azure instances, extending visibility beyond AWS. It uses enhanced Amazon Inspector SBOM analysis to identify inference endpoints, models, and AI agents on Azure VMs, including frameworks like Ollama, vLLM, and Hugging Face TGI. Discovered assets are mapped to underlying infrastructure and correlated with security findings for filtering and querying across AWS and Azure. This capability is included with Security Hub Essentials at no extra cost and is available in all commercial Regions where Security Hub is offered.
read more β†’

Agentic Security: Detection and Response at Machine Speed

πŸ”’ AWS outlines how the rise of autonomous AI agents demands a shift in security posture from event-driven to continuous, machine-speed detection and response. The post summarizes a collaborative chapter with the SANS Institute in the 2026 Cloud Security Exchange eBook, emphasizing that existing security principlesβ€”identity governance, least privilege, and defense in depthβ€”must be adapted for probabilistic, autonomous workloads. AWS highlights built-in platform services like Amazon GuardDuty, Amazon Inspector, and AWS Security Hub as components to extend trusted controls for agentic AI adoption.
read more β†’

AWS partners with Upwind to extend Security Hub

πŸ”’ AWS invited Upwind to join Security Hub Extended after customers repeatedly cited Upwind as a complementary solution. Upwind integrated deeply, offering runtime-first protection, pay-as-you-go pricing, and aligned go-to-market efforts that have driven strong joint deal activity. The integration enables unified findings in OCSF across build-to-runtime tools, simplified procurement on one AWS bill, and no custom integrations for customers.
read more β†’

AWS Security Hub Extended Adds Supply Chain Security

πŸ”’ AWS Security Hub Extended has added Supply Chain Security as its tenth curated category, expanding the program to 23 partners. The launch features Chainguard and Socket as integrated partners, offering rebuilt, provenance-backed open source packages and behavioral package analysis respectively. Both offerings are available via pay-as-you-go pricing or Private Offers for committed terms, and findings flow into Security Hub in OCSF to correlate supply chain risk with other security signals. The move aims to reduce activation friction and enable cross-partner correlation across endpoint, identity, cloud, and more.
read more β†’

Route Bedrock Guardrails Interventions to Security Lake

πŸ”’ This post shows how to route Amazon Bedrock Guardrails intervention events into Amazon Security Lake by transforming model invocation logs into OCSF-compliant Detection Finding records. It outlines an automated pipeline using CloudWatch Logs subscription filters, an AWS Lambda transformer, Parquet output, and Security Lake partitions so analysts can query guardrail events alongside identity, network, and application telemetry. The solution maps guardrail fields to OCSF attributes, supports multi-account deployment, and offers scaling guidance and an alternative CloudWatch-only approach.
read more β†’