Beginning today, customers can use Amazon Bedrock in the Africa (Cape Town), Canada West (Calgary), Mexico (Central), and Middle East (Bahrain) regions to easily build and scale generative AI applications using a variety of foundation models (FMs) as well as powerful tools to build generative AI applications.
Amazon Bedrock is a comprehensive and secure service for building generative AI applications and agents. Amazon Bedrock connects you to leading foundation models (FMs) and services to deploy and operate agents, enabling you to quickly move from experimentation to real-world deployment.
Beginning today, customers can use Amazon Bedrock in the Africa (Cape Town), Canada West (Calgary), Mexico (Central), and Middle East (Bahrain) regions to easily build and scale generative AI applications using a variety of foundation models (FMs) as well as powerful tools to build generative AI applications. Amazon Bedrock is a comprehensive and secure service for building generative AI applications and agents. Amazon Bedrock connects you to leading foundation models (FMs) and services to deploy and operate agents, enabling you to quickly move from experimentation to real-world deployment. To get started, visit the Amazon Bedrock page and see the Amazon Bedrock documentation for more details.
Amazon Inspector can now be enabled, configured and managed across your organization using AWS Org policies. With this new capability, you can centrally configure and manage scan types—such as Amazon EC2 scanning, ECR scanning, Lambda standard and Code Scanning, and Code Security — across all the accounts in your organization, selected organizational units (OUs), or individual accounts. The new Inspector policy type within AWS Organization simplifies your service onboarding, management, and ensures consistent, organization-wide vulnerability scanning coverage.
This feature helps you maintain a uniform security baseline by automating Inspector enablement through a single AWS Organization policy. To get started, designate a delegated admin within Amazon Inspector, enable the “Inspector policies” policy type in the AWS Organizations console, and create a policy that specifies the desired scan types and Regions. Once attached to your organization root or OUs, Inspector will automatically be enabled for all the specified scan-types across covered accounts . When the Inspector policy is created and attached, all in-scope accounts automatically are aligned with your Organization-wide policy definition. New accounts that join the organization or are moved into an OU with an attached policy, inherit Inspector enablement automatically—reducing operational overhead and eliminating coverage gaps.
Amazon Inspector is a vulnerability management service that continuously scans AWS workloads including Amazon EC2 instances, container images, AWS Lambda functions, and code repositories for software vulnerabilities, code vulnerabilities, and unintended network exposure across your entire AWS organization. The AWS Organizations Inspector policy for organization-wide enablement is available at no additional cost to Amazon Inspector customers in all AWS commercial, China, and AWS GovCloud (US) Regions where Amazon Inspector is available.
To learn more about Amazon Inspector policies within AWS Organization, visit:
Amazon Inspector can now be enabled, configured and managed across your organization using AWS Org policies. With this new capability, you can centrally configure and manage scan types—such as Amazon EC2 scanning, ECR scanning, Lambda standard and Code Scanning, and Code Security — across all the accounts in your organization, selected organizational units (OUs), or individual accounts. The new Inspector policy type within AWS Organization simplifies your service onboarding, management, and ensures consistent, organization-wide vulnerability scanning coverage. This feature helps you maintain a uniform security baseline by automating Inspector enablement through a single AWS Organization policy. To get started, designate a delegated admin within Amazon Inspector, enable the “Inspector policies” policy type in the AWS Organizations console, and create a policy that specifies the desired scan types and Regions. Once attached to your organization root or OUs, Inspector will automatically be enabled for all the specified scan-types across covered accounts . When the Inspector policy is created and attached, all in-scope accounts automatically are aligned with your Organization-wide policy definition. New accounts that join the organization or are moved into an OU with an attached policy, inherit Inspector enablement automatically—reducing operational overhead and eliminating coverage gaps. Amazon Inspector is a vulnerability management service that continuously scans AWS workloads including Amazon EC2 instances, container images, AWS Lambda functions, and code repositories for software vulnerabilities, code vulnerabilities, and unintended network exposure across your entire AWS organization. The AWS Organizations Inspector policy for organization-wide enablement is available at no additional cost to Amazon Inspector customers in all AWS commercial, China, and AWS GovCloud (US) Regions where Amazon Inspector is available. To learn more about Amazon Inspector policies within AWS Organization, visit:
Getting started with Amazon Inspector
Managing organization policies with AWS Organizations
AWS announced expanded capabilities in Amazon Bedrock Guardrails for code-related use cases, enabling customers to protect against harmful content in code while building generative AI applications. This new capability allows customers to leverage existing safeguards offered by Bedrock Guardrails including content filters, denied topics, and sensitive information filters to detect intent to inject malicious code, detect and prevent prompt leakages, and help protect against introducing personally identifiable information (PII) within code.
With expanded support for code-related use cases, Amazon Bedrock Guardrails now provides customers with safeguards against harmful content introduced within code elements, including comments, variable and function names, and string literals. Content filters (with standard tier) in Bedrock Guardrails now detect and filter such harmful content in code in the same way as text and image content protection. Additionally, Bedrock Guardrails offers enhanced protection with prompt leakage detection with standard tier, helping detect and prevent unintended disclosure of information from system prompts in model responses that could compromise intellectual property. Furthermore, denied topics (with standard tier) and sensitive information filters with Bedrock Guardrails now help safeguard against vulnerabilities using code within topics and help prevent inclusion of PII within code structures.
The expanded capabilities for code-related cases is available in all AWS Regions where Amazon Bedrock Guardrails is supported. Customers can access the service through the Amazon Bedrock console, as well as the supported APIs.
AWS announced expanded capabilities in Amazon Bedrock Guardrails for code-related use cases, enabling customers to protect against harmful content in code while building generative AI applications. This new capability allows customers to leverage existing safeguards offered by Bedrock Guardrails including content filters, denied topics, and sensitive information filters to detect intent to inject malicious code, detect and prevent prompt leakages, and help protect against introducing personally identifiable information (PII) within code. With expanded support for code-related use cases, Amazon Bedrock Guardrails now provides customers with safeguards against harmful content introduced within code elements, including comments, variable and function names, and string literals. Content filters (with standard tier) in Bedrock Guardrails now detect and filter such harmful content in code in the same way as text and image content protection. Additionally, Bedrock Guardrails offers enhanced protection with prompt leakage detection with standard tier, helping detect and prevent unintended disclosure of information from system prompts in model responses that could compromise intellectual property. Furthermore, denied topics (with standard tier) and sensitive information filters with Bedrock Guardrails now help safeguard against vulnerabilities using code within topics and help prevent inclusion of PII within code structures. The expanded capabilities for code-related cases is available in all AWS Regions where Amazon Bedrock Guardrails is supported. Customers can access the service through the Amazon Bedrock console, as well as the supported APIs. To learn more, read the launch blog, technical documentation, and the Bedrock Guardrails product page.
AWS Cost Optimization Hub, a feature within the Billing and Cost Management Console, now supports a Cost Efficiency metric that helps you measure and track cloud cost efficiency over time across your organization. This metric automatically calculates the percentage of your cloud spend that can be optimized by considering rightsizing, idle, and commitment recommendations, allowing you to establish consistent cost savings benchmarks, set performance goals, and track progress to maximize your return on cloud investments.
AWS Cost Optimization Hub provides you with a measure of your cost efficiency by dividing aggregated estimated monthly savings of your cost optimization opportunities by your optimizable spend. You can track this metric over time across your organization to understand and benchmark your cost efficiency. With daily refreshes, the metric provides daily insights into optimization progress, showing score improvements when you implement cost-saving recommendations and score decreases when inefficient resources are provisioned.
Cost efficiency is now available in AWS Cost Optimization Hub across all AWS Regions where AWS Cost Optimization Hub is supported. To get started with cost efficiency metric, please visit the user guide and blog.
AWS Cost Optimization Hub, a feature within the Billing and Cost Management Console, now supports a Cost Efficiency metric that helps you measure and track cloud cost efficiency over time across your organization. This metric automatically calculates the percentage of your cloud spend that can be optimized by considering rightsizing, idle, and commitment recommendations, allowing you to establish consistent cost savings benchmarks, set performance goals, and track progress to maximize your return on cloud investments. AWS Cost Optimization Hub provides you with a measure of your cost efficiency by dividing aggregated estimated monthly savings of your cost optimization opportunities by your optimizable spend. You can track this metric over time across your organization to understand and benchmark your cost efficiency. With daily refreshes, the metric provides daily insights into optimization progress, showing score improvements when you implement cost-saving recommendations and score decreases when inefficient resources are provisioned. Cost efficiency is now available in AWS Cost Optimization Hub across all AWS Regions where AWS Cost Optimization Hub is supported. To get started with cost efficiency metric, please visit the user guide and blog.
AWS Channel Partners who are part of AWS Solution Provider or Distribution program can now resell AWS services using Billing Transfer. Billing Transfer enables Partners to assume financial responsibility for customer AWS Organizations while customers retain full control of their management accounts. Using Billing Transfer with AWS Partner Central channel management, Partners receive eligible program benefits applied to AWS bills delivered to their AWS Organization, while end customers view their costs at Partner-configured rates within their separate AWS Organization.
Billing Transfer helps all AWS Channel Partners simplify operations by centrally managing billing and payments across many customer AWS Organizations from a single partner management account. Partners can also now use new APIs for Partner Central to manage channel program reporting and incentive qualification from their own systems. End customers gain autonomy to independently manage their AWS Organizations while benefiting from Partner value-added services such as cost optimization and service management.
Billing Transfer is available to all AWS Channel Partners and their end customers operating in public AWS Regions, excluding the AWS GovCloud (US), China (Beijing), and China (Ningxia) Regions.
Channel Partners can get started today through AWS Partner Central channel management. To learn more, see the Channel management user guide in Partner Central documentation and read the AWS Blog.
AWS Channel Partners who are part of AWS Solution Provider or Distribution program can now resell AWS services using Billing Transfer. Billing Transfer enables Partners to assume financial responsibility for customer AWS Organizations while customers retain full control of their management accounts. Using Billing Transfer with AWS Partner Central channel management, Partners receive eligible program benefits applied to AWS bills delivered to their AWS Organization, while end customers view their costs at Partner-configured rates within their separate AWS Organization. Billing Transfer helps all AWS Channel Partners simplify operations by centrally managing billing and payments across many customer AWS Organizations from a single partner management account. Partners can also now use new APIs for Partner Central to manage channel program reporting and incentive qualification from their own systems. End customers gain autonomy to independently manage their AWS Organizations while benefiting from Partner value-added services such as cost optimization and service management. Billing Transfer is available to all AWS Channel Partners and their end customers operating in public AWS Regions, excluding the AWS GovCloud (US), China (Beijing), and China (Ningxia) Regions. Channel Partners can get started today through AWS Partner Central channel management. To learn more, see the Channel management user guide in Partner Central documentation and read the AWS Blog.
Amazon Web Services (AWS) announces regional availability mode for NAT Gateways. With this launch, you can create a single NAT Gateway that automatically expands and contracts across availability zones (AZs) in your Virtual Private Cloud (VPC) based on your workload presence, to maintain high availability while offering simplified setup and management.
A NAT Gateway enables instances in a private subnet to connect to services outside your VPC using the NAT Gateway’s IP address. With this launch, you can create a NAT Gateway and set its availability to regional. You do not need a public subnet to host a regional NAT Gateway. You also do not have to create and delete NAT Gateways, and edit your route tables every time your workloads expand to new availability zones. You simply create a NAT Gateway with regional mode, choose your VPC, and it automatically expands and contracts across all availability zones based on your workload’s presence, maintaining high availability. You can use this feature with Amazon provided IP addresses or bring your own IP addresses.
This capability is available in all commercial AWS Regions, except the AWS GovCloud (US) Regions and the China Regions. To learn more about VPC NAT Gateway and this feature, please visit our documentation.
Amazon Web Services (AWS) announces regional availability mode for NAT Gateways. With this launch, you can create a single NAT Gateway that automatically expands and contracts across availability zones (AZs) in your Virtual Private Cloud (VPC) based on your workload presence, to maintain high availability while offering simplified setup and management. A NAT Gateway enables instances in a private subnet to connect to services outside your VPC using the NAT Gateway’s IP address. With this launch, you can create a NAT Gateway and set its availability to regional. You do not need a public subnet to host a regional NAT Gateway. You also do not have to create and delete NAT Gateways, and edit your route tables every time your workloads expand to new availability zones. You simply create a NAT Gateway with regional mode, choose your VPC, and it automatically expands and contracts across all availability zones based on your workload’s presence, maintaining high availability. You can use this feature with Amazon provided IP addresses or bring your own IP addresses. This capability is available in all commercial AWS Regions, except the AWS GovCloud (US) Regions and the China Regions. To learn more about VPC NAT Gateway and this feature, please visit our documentation.
AWS today announced the general availability of Reserved Instances and Savings Plans (RISP) Group Sharing, a new Billing and Cost Management feature that gives customers granular control over how AWS commitments are shared across their organization. This capability allows customers to define how Reserved Instances and Savings Plans benefits are distributed among specific groups of accounts within their AWS organization, ensuring cost savings align with their business structure and accountability requirements.
RISP Group Sharing addresses a common challenge faced by enterprise customers managing AWS costs across multiple business units: for example, Reserved Instances and Savings Plans don’t always benefit the teams that purchased them. With this feature, customers can create groups using AWS Cost Categories that reflect their organizational hierarchy—whether by business units, projects, geographical regions, or funding sources. The feature offers two sharing options: the Prioritized Group Sharing applies commitments to defined groups first, then shares unused capacity organization-wide, while the Restricted Group Sharing keeps commitments exclusively within defined groups for complete isolation when strict boundaries are required.
RISP Group Sharing is available now in all AWS Regions, except AWS GovCloud (US) Regions and the China Regions.
To get started with RISP Group Sharing, visit the Billing preferencesfrom the AWS Billing and Cost Management Console and follow the guided setup to create your first Cost Category and configure sharing preferences. For detailed implementation guidance, see the user guide and announcement blog.
AWS today announced the general availability of Reserved Instances and Savings Plans (RISP) Group Sharing, a new Billing and Cost Management feature that gives customers granular control over how AWS commitments are shared across their organization. This capability allows customers to define how Reserved Instances and Savings Plans benefits are distributed among specific groups of accounts within their AWS organization, ensuring cost savings align with their business structure and accountability requirements. RISP Group Sharing addresses a common challenge faced by enterprise customers managing AWS costs across multiple business units: for example, Reserved Instances and Savings Plans don’t always benefit the teams that purchased them. With this feature, customers can create groups using AWS Cost Categories that reflect their organizational hierarchy—whether by business units, projects, geographical regions, or funding sources. The feature offers two sharing options: the Prioritized Group Sharing applies commitments to defined groups first, then shares unused capacity organization-wide, while the Restricted Group Sharing keeps commitments exclusively within defined groups for complete isolation when strict boundaries are required. RISP Group Sharing is available now in all AWS Regions, except AWS GovCloud (US) Regions and the China Regions. To get started with RISP Group Sharing, visit the Billing preferences from the AWS Billing and Cost Management Console and follow the guided setup to create your first Cost Category and configure sharing preferences. For detailed implementation guidance, see the user guide and announcement blog.
Today, we’re announcing new network observability features in Amazon Elastic Kubernetes Service (EKS) that provide deeper insights into your container networking environment. These new capabilities help you better understand, monitor, and troubleshoot your Kubernetes network landscape in AWS.
Customers are increasingly deploying microservices to expand and incrementally innovate with software in the AWS cloud, while using Amazon EKS as the underlying platform to run their applications. With enhanced container network observability, customers can leverage granular, network-related metrics for better proactive anomaly detection across cluster traffic, cross-AZ flows, and AWS services. Using these metrics, customers can better measure system performance and visualize the underlying metrics using their preferred observability stack.
Additionally, EKS now provides network monitoring visualizations in the AWS console that accelerate and enhance precise troubleshooting for faster root cause analysis. Customers can also leverage these visual capabilities to pinpoint top-talkers and network flows causing retransmissions and retransmission timeouts, eliminating blind spots during incidents. These network monitoring features in EKS are powered by Amazon CloudWatch Network Flow Monitor.
Enhanced container network observability for EKS is available in all commercial AWS Regions where CloudWatch Network Flow Monitor is available. To learn more, visit the Amazon EKS documentation and AWS News Launch Blog.
Today, we’re announcing new network observability features in Amazon Elastic Kubernetes Service (EKS) that provide deeper insights into your container networking environment. These new capabilities help you better understand, monitor, and troubleshoot your Kubernetes network landscape in AWS. Customers are increasingly deploying microservices to expand and incrementally innovate with software in the AWS cloud, while using Amazon EKS as the underlying platform to run their applications. With enhanced container network observability, customers can leverage granular, network-related metrics for better proactive anomaly detection across cluster traffic, cross-AZ flows, and AWS services. Using these metrics, customers can better measure system performance and visualize the underlying metrics using their preferred observability stack. Additionally, EKS now provides network monitoring visualizations in the AWS console that accelerate and enhance precise troubleshooting for faster root cause analysis. Customers can also leverage these visual capabilities to pinpoint top-talkers and network flows causing retransmissions and retransmission timeouts, eliminating blind spots during incidents. These network monitoring features in EKS are powered by Amazon CloudWatch Network Flow Monitor. Enhanced container network observability for EKS is available in all commercial AWS Regions where CloudWatch Network Flow Monitor is available. To learn more, visit the Amazon EKS documentation and AWS News Launch Blog.
Today, AWS Secrets Manager announces the launch of managed external secrets, a feature that offers default enabled automatic rotation for your third party Software-as-a-service (SaaS) secrets. You also get an option to choose from multiple different rotation strategies that are supported by your SaaS provider, without the overhead of rotation Lambda function creation, or management. With this launch, you can secure your SaaS secrets with AWS Secrets Manager with a pre-defined secret format, as prescribed by your SaaS provider.
This launch also includes an onboarding guide, for any SaaS provider to be listed as a partner. This would allow partners to offer their customers prescriptive guidance around managing their secrets, reducing the customer overhead for managing secrets. At launch, managed external secrets feature is available for 3 listed partners — Salesforce, BigID and Snowflake.
To get started with the feature, refer to the technical documentation. The feature is available in all AWS Regions where AWS Secrets Manager is available. For a list of regions where Secrets Manager is available, see the AWS Region table.
Today, AWS Secrets Manager announces the launch of managed external secrets, a feature that offers default enabled automatic rotation for your third party Software-as-a-service (SaaS) secrets. You also get an option to choose from multiple different rotation strategies that are supported by your SaaS provider, without the overhead of rotation Lambda function creation, or management. With this launch, you can secure your SaaS secrets with AWS Secrets Manager with a pre-defined secret format, as prescribed by your SaaS provider. This launch also includes an onboarding guide, for any SaaS provider to be listed as a partner. This would allow partners to offer their customers prescriptive guidance around managing their secrets, reducing the customer overhead for managing secrets. At launch, managed external secrets feature is available for 3 listed partners — Salesforce, BigID and Snowflake. To get started with the feature, refer to the technical documentation. The feature is available in all AWS Regions where AWS Secrets Manager is available. For a list of regions where Secrets Manager is available, see the AWS Region table.
Agentes integrados en su flujo de trabajo: Obtengan Security Copilot con Microsoft 365 E5
Por: Dorothy Li, vicepresidenta corporativa, Microsoft Security Copilot y Ecosistema.
El panorama de la ciberseguridad se encuentra en un punto de inflexión histórico. Mientras los ciberatacantes emplean IA para automatizar ciberataques a una velocidad y escala extraordinarias, el reto que tenemos ante nosotros no es solo mantener el ritmo, sino adelantarse. Hay más de cuatro millones de puestos de trabajo sin cubrir en ciberseguridad, por lo que depender solo de los recursos humanos no es suficiente para proteger nuestro futuro digital.1 Para cerrar esta brecha, es importante capacitar a los profesionales de la seguridad, al mejorar sus capacidades a través de agentes inteligentes—colaboradores de IA diseñados para aumentar la experiencia humana y ayudar a transformar la seguridad organizacional.
Por eso ponemos a disposición a los agentes de seguridad en el flujo diario de trabajo de los equipos de seguridad, integrados directo en las herramientas que ustedes aman y utilizan. En Microsoft Ignite 2025, no solo anunciamos nuevas funcionalidades, sino que redefinimos lo que es posible, al empoderar a los equipos de seguridad para que pasen de respuestas reactivas a estrategias proactivas.
Desbloquear la seguridad donde la IA es primero con Microsoft Security Copilot
Una suscripción Microsoft 365 E5 ofrece seguridad en toda su organización, incluida la protección contra amenazas con Microsoft Defender, gestión de identidad y accesos mediante Microsoft Entra, gestión de terminales mediante Microsoft Intune, y seguridad de datos proporcionada por Microsoft Purview. Microsoft Security Copilot amplifica estas capacidades con agentes integrados que actúan como multiplicadores de fuerza a lo largo de toda la pila de seguridad. Los equipos de seguridad cuentan con agentes adaptativos, que trabajan codo con codo con ellos para acelerar las investigaciones, agilizar tareas y ofrecer resultados más rápidos e inteligentes.
Para facilitar el aprovechamiento de estos agentes y comenzar más rápido, nos complace anunciar que Microsoft Security Copilot estará incluido para todos los clientes de Microsoft 365 E5.* El despliegue comienza hoy para los clientes existentes de Security Copilot con Microsoft 365 E5 y continuará en los próximos meses para todos los clientes de Microsoft 365 E5.
Los clientes existentes de Security Copilot con suscripciones Microsoft 365 E5 pueden empezar hoy mismo con los agentes sin coste adicional*:
Todos los demás clientes de Microsoft 365 E5 recibirán una notificación anticipada de 30 días antes de la activación y podrán obtener más información en la documentación.
Bienvenidos a una nueva era de la ciberseguridad: donde los agentes están integrados, son fáciles de usar y están listos para ayudar a su equipo a mantenerse por delante de las ciberamenazas.
Ampliación de nuestra cartera de agentes para obtener mejores resultados en materia de valores
No solo hacemos que estos agentes sean más accesibles, sino que también ampliamos el ecosistema. En adición a los 37 agentes de Security Copilot ya disponibles, presentamos más de 40 nuevos agentes de Microsoft y de sus socios.
Hoy están disponibles en vista previa 12 nuevos agentes creados por Microsoft a través de MicrosoftDefender, Entra, Intune y Purview. Además, más de 30 nuevos agentes construidos por socios amplían la protección de extremo a extremo. Estos agentes automatizan tareas a gran escala, lo que permite a los equipos de seguridad dedicar más tiempo a iniciativas estratégicas.
Amplia cartera con nuevos agentes
Los equipos de operaciones de seguridad pueden aprovechar a los agentes que hacen triaje de las alertas en tiempo real, muestran inteligencia accionable de amenazas y permiten la búsqueda de amenazas en lenguaje natural, para que los defensores puedan centrarse en lo que más importa: adelantarse a los ciberatacantes.
Los administradores de identidad y acceso pueden desplegar nuevos agentes en Microsoft Entra para proteger a través de las capas de identidad: para remediar de manera proactiva a los usuarios riesgosos, optimizar las políticas de Acceso Condicional, agilizar revisiones de acceso y gestionar ciclos de vida de las aplicaciones para reducir riesgos y mejorar la eficiencia.
Los profesionales de la seguridad de datos pueden utilizar agentes en el ámbito de Microsoft para reforzar la seguridad de los datos al descubrir, analizar y remediar riesgos sensibles de datos, al combinar una gestión proactiva de posturas con un triaje inteligente para reducir el trabajo manual y ayudar a una reducción continua de riesgos.
Los administradores de TI pueden utilizar los nuevos agentes en Microsoft Intune para facilitar tareas complejas y reforzar la seguridad al convertir los requisitos en políticas, evaluar los cambios antes de que afecten a la productividad e identificar dispositivos para eliminar — para tomar decisiones más inteligentes, mejor cumplimiento y reducir el riesgo.
Agentes en todos los roles a través del ecosistema de socios: además, hay más de 30 nuevos agentes creados por socios disponibles hoy en la Microsoft Security Store. Estos agentes apoyan roles de seguridad en toda la industria, con habilidades y capacidades como simplificar el análisis de incidentes, mejorar la protección de datos y garantizar que las herramientas de seguridad estén alineadas con los estándares del sector. Para saber más sobre estas ofertas de agentes, visiten Microsoft Security Store.
Si no encuentran justo lo que necesitan entre las decenas de agentes listos para usar, Security Copilot les da la flexibilidad de crear los suyos propios. Desde que anunciaron esta capacidad en septiembre, los clientes ya han creado más de 370 agentes únicos, adaptados a sus entornos y diseñados para sus casos de uso específicos.
Evolución de las capacidades de los agentes para una colaboración más profunda
Con la experiencia interactiva del agente, ahora en vista previa pública, los equipos de seguridad pueden participar en chats enfocados y con alcance adaptado a la experiencia de cada agente. Los flujos de trabajo dinámicos y los prompts de inicio integrados mantienen las investigaciones en marcha, mientras que las sugerencias rápidas surgen en tiempo real, para ayudar a humanos y agentes a colaborar para obtener resultados de seguridad y TI más rápidos y efectivos.
Y para empoderar en verdad a los agentes, el contexto y los datos son clave. Security Copilot aprovecha la inteligencia de amenazas de Microsoft—impulsada por más de 100 billones de señales procesadas a diario—y unifica los conocimientos a través de Microsoft Sentinel. Ahora, con la integración del conocimiento empresarial en vista previa, los agentes pueden razonar sobre los datos internos de su organización, para ofrecer recomendaciones contextuales únicas para su entorno. Esto significa que cada interacción está informada, precisa y adaptada para acelerar sus operaciones de seguridad y TI.
Agentes aceleran los resultados de ciberseguridad
Esto no es solo visión, es realidad. Los agentes de Security Copilot ya han comenzado a ofrecer resultados transformadores:
Los analistas SOC han detectado correos maliciosos hasta un 550% más rápido con el Agente de Triaje de Phishing en Microsoft Defender, basándose en comparaciones controladas de la velocidad de detección en escenarios simulados de phishing.2
Los administradores de identidad han logrado hasta un 204% más de precisión en la identificación de políticas de Confianza Cero faltantes con el Agente de Optimización de Acceso Condicional en Microsoft Entra, medido frente a auditorías de políticas base en entornos empresariales.3
Definan el futuro de la seguridad con Microsoft
Microsoft está comprometida a ayudar a las organizaciones a convertirse en verdaderas «Empresas Frontera«: pioneras que aprovechan la IA agéntica para transformar la seguridad y las operaciones de TI. Microsoft Ignite es su invitación a formar parte de este movimiento: conecten con nuestros expertos, experimenten el futuro de primera mano y descubran cómo Security Copilot puede ayudarlos a alcanzar sus ambiciones más audaces.
Para saber más sobre las soluciones de seguridad de Microsoft, visiten nuestra página web. Agreguen el blog de Security en sus Favoritos para estar al día con nuestra cobertura experta sobre temas de seguridad. Además, síganos en LinkedIn (Microsoft Security) y X (@MSFTSecurity) para las últimas noticias y actualizaciones sobre ciberseguridad.
* Los clientes elegibles de Microsoft 365 E5 tendrán 400 Unidades de Cómputo de Seguridad (SCUs, por sus siglas en inglés) al mes por cada 1.000 licencias de usuario, hasta 10.000 SCUs al mes. Se espera que esta capacidad incluida soporte escenarios típicos. Los clientes tendrán la opción de pagar por una escalabilidad más allá de la cantidad asignada en una fecha futura con 6 dólares por SCU en régimen de pago por uso, y recibirán una notificación anticipada de 30 días cuando esta opción esté disponible. Más información.
