Web Search now available on Kiro in AWS GovCloud (US)

Kiro web search gives the agent real-time access to current information on the internet, so its answers draw on up-to-date search results and page content. The agent uses web search automatically when a question involves recent changes or topics beyond the model’s training data. Answers that use web results include citations.
Kiro enterprise administrators can turn off web search and web fetch for their organization from the Kiro console under Settings. Teams can also remove web tools from individual custom agents, or block them with capability-based permission rules.
For more details, visit the AWS GovCloud (US) documentation, the monitoring and tracking guide, or contact your AWS account team. To learn more about Kiro, visit the Kiro product page.
Quelle: aws.amazon.com

October 2026 PTG Recap: Kicking Off the 2027.1 “Indri” Cycle

Following the tradition of our Project Teams Gathering (PTG) summaries, the October 2026 PTG brought together developers, operators, and ecosystem contributors for a week of intensive cross-service alignment. With total attendance across all sessions exceeding 700 participants involved in conversations throughout the week, the community showed incredible engagement as it pivoted straight from the delivery… Read more »
The post October 2026 PTG Recap: Kicking Off the 2027.1 “Indri” Cycle appeared first on OpenStack Blog | Open Infrastructure Foundation.
Quelle: openstack.org

Azure Cloud HSM Hardware Audit Logging: Verifiable audit trails for security and compliance

Organizations running regulated and security-sensitive workloads need trusted evidence of which authenticated users performed management operations on their hardware security modules (HSMs), what actions they took, and when. Today, we are announcing Hardware Audit Logging for Azure Cloud HSM, which collects audit records generated by the HSM itself for supported management operations. Security, compliance, and operations teams can use this hardware-originated evidence for monitoring, compliance reporting, and forensic investigations.

Learn more about Azure Cloud HSM

Why hardware-generated audit evidence matters

HSMs protect some of an organization’s most sensitive cryptographic assets. The security of those assets depends not only on how keys are generated and protected, but also on how the HSM is configured and administered over time. Authentication events, user changes, policy updates, backup operations, and key lifecycle activity can all be important when teams investigate an incident, validate operational controls, or prepare evidence for an audit.

Traditional platform and application logs remain valuable, but regulated organizations often want evidence that originates as close as possible to the protected cryptographic boundary. By sourcing audit information directly from the HSM, Azure Cloud HSM provides records tied to the device performing the protected operations. This gives customers an additional layer of evidence for understanding administrative activity and validating the records incorporated into their monitoring and compliance processes.

Monitor HSM management operations with hardware-generated audit logs

Hardware Audit Logging captures a broad range of HSM management activities, including:

User authentication and session events.

User and administrator management.

Policy and configuration changes.

Key lifecycle operations.

Backup and restore activities.

Together, these events help organizations build a more complete view of how the HSM is being operated. Security teams can examine authentication and administrative activity, compliance teams can use the records as evidence for control assessments, and operations teams can investigate configuration or lifecycle changes that may affect a protected workload.

Independent, end-to-end audit verification

Customers can access human-readable audit records, the corresponding HSM-signed binary audit data, signatures, and HSM certificates needed to independently verify the authenticity and integrity of signed audit batches. This customer-controlled verification path helps connect the records used in monitoring and reporting back to the signed evidence produced by the HSM.

This approach is important because auditability is not only about collecting readable events. It is also about establishing confidence in where the records came from and whether the signed audit batches remain intact.

Maintain consistent audit coverage for supported management activity

Audit logging is enabled as an immutable HSM partition policy. This design helps maintain consistent coverage of supported management activity and reduces the risk that logging could be disabled as part of routine HSM administration. For organizations that separate cryptographic administration, security monitoring, and compliance responsibilities, continuous hardware-originated logging can support clearer oversight across those functions.

The capability is designed to complement an organization’s existing governance model. Customers remain responsible for configuring access to their monitoring environment, defining retention requirements, establishing alerting and review processes, and determining how audit evidence should be used within their control framework. Hardware Audit Logging provides the HSM-originated records and verification materials that those processes can use.

Integrate HSM audit data into security operations

Hardware Audit Logging is designed for organizations with stringent compliance and security requirements, including financial services, payment processing, government, critical infrastructure, and other highly regulated industries. These organizations may need to demonstrate that sensitive cryptographic systems are administered through controlled processes and that important management activities can be reviewed after the fact.

Audit events are delivered to Azure Monitor Log Analytics, enabling customers to incorporate HSM management activity into broader monitoring, investigation, and security operations workflows, including Microsoft Sentinel. Centralizing these events alongside other relevant operational and security data can help teams correlate HSM activity with events elsewhere in the environment, apply queries and analytics, and support established investigation and reporting workflows.

For example, a security operations team may want to review unexpected authentication activity, an administrator change, or a policy update in the context of related Azure activity. A compliance team may need evidence that privileged management operations were logged during a defined assessment period. An incident response team may need to reconstruct the sequence of HSM management events surrounding a security investigation. Hardware-originated audit records provide an important source for each of these scenarios.

Strengthen HSM auditability with verifiable evidence

Azure Cloud HSM provides more than log visibility. Readable audit records support day-to-day operations. It also provides HSM-signed binary evidence, signatures, certificates, and verification utilities behind those records, which lead to an independent way to trace each record back to the HSM that signed it.

It also allows for keeping that evidence outside the logging workflow and checking it cryptographically whenever an audit or investigation calls for it, instead of relying only on delivered text records. Teams get an audit trail they can verify for the workloads that matter most.

What does Azure Cloud HSM Hardware Audit Logging provide

It provides hardware-generated records for supported HSM management operations, sends audit events to Azure Monitor Log Analytics, and gives customers signed binary audit data and verification materials for independent validation.

Azure Cloud HSM Hardware Audit Logging availability

Hardware Audit Logging is rolling out across Azure Cloud HSM public regions and is automatically enabled for newly provisioned Azure Cloud HSM resources where the feature is available. Customers should review current Azure Cloud HSM regional availability and product documentation for the latest availability details and configuration guidance.

Review the resources below to learn about Azure Cloud HSM, configure operation audit logs, and confirm regional availability.

Overview of Azure Cloud HSM

Configure and query HSM operation audit logs for Azure Cloud HSM

Azure products available by region

Azure Cloud HSM

Manage HSMs used in the cloud.

Get started

The post Azure Cloud HSM Hardware Audit Logging: Verifiable audit trails for security and compliance appeared first on Microsoft Azure Blog.
Quelle: Azure

AWS Backup now supports cross-account management and cross-account backup in the AWS European Sovereign Cloud

AWS Backup now supports cross-account management, cross-account backup, and delegated administrators in the AWS European Sovereign Cloud (Germany) Region. These capabilities help you centrally manage, monitor, and copy backups across the accounts in your organization using AWS Organizations.
With cross-account management, you can deploy organization-wide backup policies from your AWS Organizations management account or a delegated administrator account. You can also monitor backup, copy, and restore jobs across all of your organization accounts from one place. With cross-account backup, you can copy recovery points to a backup vault in another account in your organization, which adds protection against accidental or malicious deletion in the source account. You can also register a member account as a delegated administrator, so your teams can manage backups across your organization without needing access to your management account.
There is no additional charge to use these capabilities; standard AWS Backup pricing applies. To learn more, see the AWS Backup documentation at https://docs.aws.amazon.com/aws-backup/. To get started, visit the AWS Backup console at https://console.aws.amazon.com/backup.
Quelle: aws.amazon.com

Amazon MSK Connect now supports updating connector plugins and worker configurations

Amazon MSK Connect (Amazon Managed Streaming for Apache Kafka Connect) now lets you update the custom plugin and worker configuration of an existing connector. This is useful when you need to update the custom plugin to run a new version of your connector code, for example one with updated dependencies. You can also update the worker configuration to change worker-level settings, such as switching key and value converters or tuning producer and consumer properties for throughput and latency.
Amazon MSK Connect is a fully managed service that allows you to deploy, monitor, and scale Apache Kafka Connect connectors with Amazon MSK (Managed Streaming for Apache Kafka). Previously, updating a connector’s plugin or worker configuration meant deleting the connector and recreating it – a disruptive operation that added risk and operational overhead. With this launch, you can update a connector’s plugin and worker configuration in place. The connector keeps its committed offsets, so its tasks continue processing from where they left off once the update completes.
This capability is available at no additional cost in all AWS Regions where Amazon MSK Connect is supported. To learn more, visit Amazon MSK Connect developer guide.
Quelle: aws.amazon.com