• Categoría: Noticias de Microsoft

diciembre 17, 2025

Preparar la ciberseguridad sanitaria para el futuro: lo que todo líder debería saber

Por: Kees Hertogh, vicepresidente de marketing del sector público y sanidad en Microsoft.

La ciberseguridad sanitaria no se trata solo de tecnología: se trata de personas, confianza y el futuro de la atención.

Los líderes sanitarios hoy en día navegan por un panorama de ciberamenazas crecientes y una mayor complejidad operativa. La ciberseguridad no es solo un requisito técnico: es esencial para generar confianza en el paciente, garantizar la continuidad de la atención y facilitar la innovación futura en el sector sanitario.

Descarguen el libro electrónico de seguridad sanitaria

En la Cumbre CISO del Instituto Scottsdale 2025, los principales líderes de seguridad se reunieron para compartir historias reales, grandes desafíos y soluciones prácticas para mantener los datos de los pacientes seguros en un mundo que cambia con rapidez. Como seguimiento, publicaron un informe sobre el Futuro para la Ciberseguridad Sanitaria: IA, Transformación en la Nube y Capacidades para el Mañana.

Aquí tienen algunos puntos destacados:

Por qué la ciberseguridad es más importante que nunca

La sanidad es un sector que es blanco de ataques de manera frecuente y con una fuerte regulación, con los resultados para los pacientes en juego.

• Las amenazas cibernéticas evolucionan con rapidez. La IA y la transformación en la nube abren nuevas puertas para la atención, pero también nuevos riesgos. Los ciberdelincuentes se vuelven más inteligentes y las organizaciones sanitarias deben mantener el paso para proteger la información sensible y ayudar a garantizar la seguridad del paciente.
• Es personal. Los líderes sanitarios nos recordaron que cada decisión de seguridad afecta a personas reales: pacientes, familias y personal. El objetivo siempre es ofrecer la mejor atención y de forma segura.

Lo que los equipos sanitarios deben saber sobre ciberseguridad

1. La colaboración es fundamental

CEOs, CIOs y CISOs deben trabajar juntos. La innovación y la seguridad van de la mano, y las sólidas alianzas ayudan a las organizaciones a mantenerse por delante de las amenazas.

2. Oportunidades y desafíos de IA

La IA puede hacer que la sanidad sea más inteligente y eficiente, pero también introduce nuevos riesgos. Los líderes deben plantearse preguntas difíciles sobre cómo las herramientas de IA utilizan los datos, cómo se forman y cómo mantenerlos seguros.

3. Formación y mejora de habilidades

Invertir en tecnología es solo la mitad de la batalla. El personal necesita formación continua para utilizar nuevas herramientas de forma segura y eficaz. Los incentivos creativos —como el tiempo de formación remunerado o las trayectorias profesionales— ayudan a los equipos a crecer y adaptarse.

4. Desmantelar compartimentos

Las estructuras heredadas pueden ralentizar el progreso. Los equipos integrados y la colaboración multifuncional son clave para encontrar y corregir vulnerabilidades con rapidez.

5. Gestión de riesgos de terceros

Las relaciones con proveedores son más complejas que nunca. Las organizaciones deben elevar el listón para las evaluaciones de proveedores, garantizar la continuidad del negocio y educar a los usuarios sobre los riesgos.

6. Resiliencia y respuesta

La prevención es importante, pero la detección y la respuesta rápida son esenciales. Las herramientas impulsadas por IA pueden ayudar a detectar comportamientos sospechosos, pero la supervisión humana sigue siendo crucial.

La seguridad del paciente, la continuidad de la atención y la confianza en la atención sanitaria dependen de mantener la ciberseguridad correctamente

Las organizaciones sanitarias se enfrentan a un punto de inflexión crítico. El éxito requerirá:

• Adoptar defensas impulsadas por IA
• Construir redes más sólidas entre los profesionales de la seguridad
• Acelerar la sofisticación de los proveedores
• Desarrollo de protocolos ágiles de respuesta a incidentes

Seguridad primero en acción: Red de Salud de St. Luke

Para la Red de Salud de la Universidad St. Luke’s, proteger los datos de los pacientes es clave para ofrecer una atención de calidad. Atiende a personas en Pensilvania y Nueva Jersey en 13 hospitales y 607 consultas, incluidas varias especialidades, y cuenta con un patrimonio de datos considerable que proteger.

Lograr esa misión vital se hizo más fácil cuando St. Luke’s redujo su número de herramientas de seguridad y obtuvo una visibilidad mucho mayor sobre los datos que necesita para mantener la seguridad.

Sustituyó varias soluciones de seguridad de terceros por Microsoft Sentinel, Microsoft Defender for Cloud y Microsoft Defender for Office 365, para ampliar su base de soluciones de seguridad de Microsoft, lo que permite una postura de seguridad unificada que ayuda a los equipos de seguridad a hacer lo que mejor saben hacer: proteger St. Luke’s de un panorama de amenazas en constante evolución.

Creo que tal vez sea la primera empresa a punto de crear el modelo predictivo que nos llevará más allá de la detección de amenazas y permitirá la prevención. Por eso confiamos en Microsoft.

–David Finkelstein, director de seguridad de la información, Red de Salud de la Universidad St. Luke’s

Construyamos juntos un futuro seguro para la sanidad

En Microsoft, nos centramos en ayudar a las organizaciones a consolidar capacidades de seguridad fragmentadas y aplicar inteligencia para obtener mejores resultados. Desde el lanzamiento de la Iniciativa Futuro Seguro (SFI, por sus siglas en inglés) en noviembre de 2023, Microsoft ha movilizado el equivalente a más de 34.000 ingenieros para mitigar riesgos y mejorar la seguridad tanto para Microsoft como para nuestros clientes.¹

Guiados por tres principios de seguridad—seguros por diseño, por defecto y en las operaciones—hemos logrado avances medibles en las áreas de cultura, gobernanza y nuestros seis pilares de ingeniería. Aun así, queda mucho por hacer, y los equipos de toda la empresa trabajan para mejorar la seguridad de cada producto, abordar los aprendizajes de cada incidente y mejorar de manera continua nuestros métodos y prácticas.

Microsoft ha sido líder durante años en el desarrollo de tecnologías de IA conforme a principios responsables de IA diseñados para cumplir con los requisitos de cumplimiento, proteger datos y sistemas, y mantener la confianza del cliente.

Descubran cómo la IA puede ayudar a reforzar la seguridad y el cumplimiento sanitario

• Descarguen el libro electrónico de seguridad sanitaria.
• Consulten la infografía de seguridad y cumplimiento sanitario.
• Para obtener información sobre cómo adelantarse a los retos y amenazas emergentes de la IA y la seguridad de la IA, consulten el Informe de Decisión de IA en la Salud 2025.
• Exploren las soluciones de seguridad de Microsoft.
• Sigan nuestras actualizaciones de ciberseguridad en Microsoft Security, LinkedIn y en X @MSFTSecurity.
• Lean el informe completo de la Cumbre CISO 2025 del Instituto Scottsdale.

¹Informe de progreso de la Iniciativa Futuro Seguro, noviembre de 2025, Microsoft

Etiquetas:

• Salud
• Seguridad

The post Preparar la ciberseguridad sanitaria para el futuro: lo que todo líder debería saber appeared first on Source LATAM.

​The post Preparar la ciberseguridad sanitaria para el futuro: lo que todo líder debería saber appeared first on Source LATAM.  

Amazon Connect alerts on real-time metrics now provide the specific agents, queues, flows, or routing profiles that exceeded thresholds and triggered the alert. This enables managers to respond faster to customer experience and operational issues by eliminating the need to manually investigate the root cause of the alert. For example, alerts on elevated queue wait times now include the exact queues affected, so managers can reassign agents to those queues. These detailed alerts can be sent through email, tasks, and Amazon EventBridge.

This feature is available in all regions where Amazon Connect is offered. To learn more, please visit our documentation and our webpage.

​Amazon Connect alerts on real-time metrics now provide the specific agents, queues, flows, or routing profiles that exceeded thresholds and triggered the alert. This enables managers to respond faster to customer experience and operational issues by eliminating the need to manually investigate the root cause of the alert. For example, alerts on elevated queue wait times now include the exact queues affected, so managers can reassign agents to those queues. These detailed alerts can be sent through email, tasks, and Amazon EventBridge. This feature is available in all regions where Amazon Connect is offered. To learn more, please visit our documentation and our webpage.  

AWS Security Incident Response now offers integration with the cloud-based team collaboration platform Slack, enabling you to prepare for, respond to, and recover from security events faster and more effectively while maintaining your existing notification and communication workflows. With the bidirectional integration, you can create and update cases in both the Security Incident Response console and Slack with automatic data replication. Each Security Incident Response case is represented as a dedicated Slack channel, while comments and attachments sync instantly. This gives responders immediate access to critical case information and enables more efficient collaboration regardless of tool preference.

The integration helps security teams engage faster and accelerate response times by automatically adding Security Incident Response watchers to the corresponding Slack channel. This integration is available as an open-source solution on GitHub, providing customers and partners the opportunity to customize and extend the functionality. The integration leverages EventBridge which allows customers to continue using their existing security incident management and notification tooling, while leveraging AWS Security Incident Response capabilities. The solution features a modular architecture, and includes guidance on how to use Amazon Q Developer, Kiro, or similar AI assistants that help make it easy to add new integration targets beyond Slack.

To get started with the AWS Security Incident Response Slack integration, visit our GitHub repository. Visit our technical documentation for Slack for implementation details. Learn more about AWS Security Incident Response in the service’s User Guide.

​AWS Security Incident Response now offers integration with the cloud-based team collaboration platform Slack, enabling you to prepare for, respond to, and recover from security events faster and more effectively while maintaining your existing notification and communication workflows. With the bidirectional integration, you can create and update cases in both the Security Incident Response console and Slack with automatic data replication. Each Security Incident Response case is represented as a dedicated Slack channel, while comments and attachments sync instantly. This gives responders immediate access to critical case information and enables more efficient collaboration regardless of tool preference. The integration helps security teams engage faster and accelerate response times by automatically adding Security Incident Response watchers to the corresponding Slack channel. This integration is available as an open-source solution on GitHub, providing customers and partners the opportunity to customize and extend the functionality. The integration leverages EventBridge which allows customers to continue using their existing security incident management and notification tooling, while leveraging AWS Security Incident Response capabilities. The solution features a modular architecture, and includes guidance on how to use Amazon Q Developer, Kiro, or similar AI assistants that help make it easy to add new integration targets beyond Slack. To get started with the AWS Security Incident Response Slack integration, visit our GitHub repository. Visit our technical documentation for Slack for implementation details. Learn more about AWS Security Incident Response in the service’s User Guide.  

AWS IoT Device Management commands now supports dynamic payload functionality, enabling developers to create reusable command templates with placeholders that can be replaced with different values during command execution. The enhancement also includes parameter validation rules to verify that parameter values conform to specified criteria before execution. With this update, developers can now set parameters for the command during runtime, making it easier for them to re-use a command.

This feature is ideal for scenarios where you need to send similar commands with different parameter values to your Internet of Things (IoT) devices. For example, instead of creating separate commands to set different temperature values of a thermostat, you can now create one template with a temperature placeholder and specify the actual value during runtime. This template-based approach helps streamline command management for applications, such as adjusting device configurations or controlling smart home devices with variable settings. 

AWS IoT Device Management commands with dynamic payload support is available in all AWS Regions where AWS IoT Device Management is currently available. To learn more about dynamic payloads and payload templates, visit AWS IoT Device Management Commands Developer Guide.

​AWS IoT Device Management commands now supports dynamic payload functionality, enabling developers to create reusable command templates with placeholders that can be replaced with different values during command execution. The enhancement also includes parameter validation rules to verify that parameter values conform to specified criteria before execution. With this update, developers can now set parameters for the command during runtime, making it easier for them to re-use a command. This feature is ideal for scenarios where you need to send similar commands with different parameter values to your Internet of Things (IoT) devices. For example, instead of creating separate commands to set different temperature values of a thermostat, you can now create one template with a temperature placeholder and specify the actual value during runtime. This template-based approach helps streamline command management for applications, such as adjusting device configurations or controlling smart home devices with variable settings. 
AWS IoT Device Management commands with dynamic payload support is available in all AWS Regions where AWS IoT Device Management is currently available. To learn more about dynamic payloads and payload templates, visit AWS IoT Device Management Commands Developer Guide.  

Today, AWS announced the opening of a new AWS Direct Connect location within the CMC Tower in Hanoi, Vietnam. You can now establish private, direct network access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones from this location. This site is the first AWS Direct Connect location in Vietnam. This Direct Connect location offers dedicated 1 Gbps, 10 Gbps, and 100 Gbps connections, with MACsec encryption available for 10 Gbps and 100 Gbps connections. 

The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet. 

For more information on the over 149 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.

​Today, AWS announced the opening of a new AWS Direct Connect location within the CMC Tower in Hanoi, Vietnam. You can now establish private, direct network access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones from this location. This site is the first AWS Direct Connect location in Vietnam. This Direct Connect location offers dedicated 1 Gbps, 10 Gbps, and 100 Gbps connections, with MACsec encryption available for 10 Gbps and 100 Gbps connections.  The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet.  For more information on the over 149 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.  

Starting today, you can build, train, and deploy machine learning (ML) models in Asia Pacific (New Zealand).

Amazon SageMaker AI is a fully managed platform that provides every developer and data scientist with the ability to build, train, and deploy machine learning (ML) models quickly. SageMaker AI removes the heavy lifting from each step of the machine learning process to make it easier to develop high quality models.

To learn more and get started, see SageMaker AI documentation and pricing page.

​Starting today, you can build, train, and deploy machine learning (ML) models in Asia Pacific (New Zealand). Amazon SageMaker AI is a fully managed platform that provides every developer and data scientist with the ability to build, train, and deploy machine learning (ML) models quickly. SageMaker AI removes the heavy lifting from each step of the machine learning process to make it easier to develop high quality models.
To learn more and get started, see SageMaker AI documentation and pricing page.  

AWS is now publishing your carbon footprint data in 21 days or less. Previously, the carbon footprint data was published with up to a three month data lag. Now, you have access to your carbon footprint data with estimates published between the 15th and the 21st of the month following your usage.

With carbon footprint data available sooner, you have the insights needed to make more timely decisions about how and where your applications are running and identify opportunities to reduce emissions and costs through improved resource efficiency. Also, the CCFT dashboard maintains 38 months of data so you can view your carbon usage trends over time.

To view your carbon footprint data, navigate to your carbon emissions data through the AWS Billing and Cost Management console. For more information about CCFT visit the CCFT capabilities and features page, review the CCFT user guides, and learn more by visiting the CCFT webpage.

​AWS is now publishing your carbon footprint data in 21 days or less. Previously, the carbon footprint data was published with up to a three month data lag. Now, you have access to your carbon footprint data with estimates published between the 15th and the 21st of the month following your usage. With carbon footprint data available sooner, you have the insights needed to make more timely decisions about how and where your applications are running and identify opportunities to reduce emissions and costs through improved resource efficiency. Also, the CCFT dashboard maintains 38 months of data so you can view your carbon usage trends over time. To view your carbon footprint data, navigate to your carbon emissions data through the AWS Billing and Cost Management console. For more information about CCFT visit the CCFT capabilities and features page, review the CCFT user guides, and learn more by visiting the CCFT webpage.  

Starting today, Amazon EC2 M8i instances are now available in Asia Pacific (Seoul), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Singapore), and Canada (Central) Regions. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. The M8i offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances. They deliver up to 20% better performance than M7i instances, with even higher gains for specific workloads. The M8i instances are up to 30% faster for PostgreSQL databases, up to 60% faster for NGINX web applications, and up to 40% faster for AI deep learning recommendation models compared to M7i instances.

M8i instances are a great choice for all general purpose workloads, especially for workloads that need the largest instance sizes or continuous high CPU usage. The SAP-certified M8i instances offer 13 sizes including 2 bare metal sizes and the new 96xlarge size for the largest applications.

To get started, sign in to the AWS Management Console. For more information about the new instances, visit the M8i instance page or visit the AWS News blog.

​Starting today, Amazon EC2 M8i instances are now available in Asia Pacific (Seoul), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Singapore), and Canada (Central) Regions. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. The M8i offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances. They deliver up to 20% better performance than M7i instances, with even higher gains for specific workloads. The M8i instances are up to 30% faster for PostgreSQL databases, up to 60% faster for NGINX web applications, and up to 40% faster for AI deep learning recommendation models compared to M7i instances. M8i instances are a great choice for all general purpose workloads, especially for workloads that need the largest instance sizes or continuous high CPU usage. The SAP-certified M8i instances offer 13 sizes including 2 bare metal sizes and the new 96xlarge size for the largest applications. To get started, sign in to the AWS Management Console. For more information about the new instances, visit the M8i instance page or visit the AWS News blog.  

AWS Artifact now enables direct access to previous versions of AWS compliance reports, eliminating the need to contact AWS Support or account representatives. This self-service capability helps customers efficiently manage their compliance documentation requirements, particularly during audits and vendor assessments that require historical compliance evidence.

To access previous report versions, you need the «artifact:ListReportVersions» IAM permission, which is included in the AWS managed policy «AWSArtifactReportsReadOnlyAccess». If you’re unable to view previous versions of reports in the AWS Artifact console, please contact your AWS account administrator to request this permission.

Once authorized, you can access previous versions of compliance reports (such as SOC, ISO, and C5) directly through the AWS Artifact console. Simply navigate to the reports page and select any report to view its available versions. The availability of previous report versions varies by compliance program, with some reports offering versions from multiple prior years while others may have more limited historical coverage.

This feature is now generally available in US East (N. Virginia) and AWS GovCloud (US-West) Regions.

To learn more about accessing previous versions of compliance reports, visit the AWS Artifact documentation. For general information about AWS Artifact, see the AWS Artifact product page.

​AWS Artifact now enables direct access to previous versions of AWS compliance reports, eliminating the need to contact AWS Support or account representatives. This self-service capability helps customers efficiently manage their compliance documentation requirements, particularly during audits and vendor assessments that require historical compliance evidence. To access previous report versions, you need the «artifact:ListReportVersions» IAM permission, which is included in the AWS managed policy «AWSArtifactReportsReadOnlyAccess». If you’re unable to view previous versions of reports in the AWS Artifact console, please contact your AWS account administrator to request this permission. Once authorized, you can access previous versions of compliance reports (such as SOC, ISO, and C5) directly through the AWS Artifact console. Simply navigate to the reports page and select any report to view its available versions. The availability of previous report versions varies by compliance program, with some reports offering versions from multiple prior years while others may have more limited historical coverage. This feature is now generally available in US East (N. Virginia) and AWS GovCloud (US-West) Regions. To learn more about accessing previous versions of compliance reports, visit the AWS Artifact documentation. For general information about AWS Artifact, see the AWS Artifact product page.  

We are announcing memory for chat agents in Amazon Quick Suite – a feature that allows users to get personalized responses based on their previous conversations. With this feature, Quick Suite remembers the preferences users specify in chat and generate responses that are tailored to them. Users can also view their inferred preferences and remove any memory they don’t want Quick chat agents to use.

Previously, chat users needed to repeat their preferences around response format, acronyms, dashboards, and integrations in every conversation. They also had to clarify ambiguous topics and entities in chat, increasing the tedious back and forth needed to get accurate and insightful responses. Memory addresses this pain point by remembering facts and details about users in a way that ensures responses provided to users continuously learn and improve. Users also control what Quick Suite remembers about them – all the memories are viewable and removable by users, and users have the choice to start chat in Private Mode in which conversations are not used to infer memories.

Memory in Quick Suite chat agents is available in US East (N. Virginia) and US West (Oregon). To learn more, visit the Amazon Quick Suite User Guide.

​We are announcing memory for chat agents in Amazon Quick Suite – a feature that allows users to get personalized responses based on their previous conversations. With this feature, Quick Suite remembers the preferences users specify in chat and generate responses that are tailored to them. Users can also view their inferred preferences and remove any memory they don’t want Quick chat agents to use. Previously, chat users needed to repeat their preferences around response format, acronyms, dashboards, and integrations in every conversation. They also had to clarify ambiguous topics and entities in chat, increasing the tedious back and forth needed to get accurate and insightful responses. Memory addresses this pain point by remembering facts and details about users in a way that ensures responses provided to users continuously learn and improve. Users also control what Quick Suite remembers about them – all the memories are viewable and removable by users, and users have the choice to start chat in Private Mode in which conversations are not used to infer memories. Memory in Quick Suite chat agents is available in US East (N. Virginia) and US West (Oregon). To learn more, visit the Amazon Quick Suite User Guide.