CEA-Leti and Soitec are to use the natural attributes of fully-depleted silicon-on-insulator (FD-SOI) to enhance the cybersecurity of integrated circuits. “With FD-SOI’s advantages against laser fault injection attacks due to …

The post Silicon-on-insulator for cybersecurity appeared first on Electronics Weekly .

AWS announces an enhanced AWS Security Hub to prioritize your critical security issues and help respond at scale to reduce security risks, improve your team’s productivity, and protect your cloud environment. It detects critical issues by correlating and enriching security signals, for example, from threat detection and vulnerability management. This enables you to quickly surface and prioritize active risks in your cloud environment. The unified solution provides more comprehensive visibility into your security posture while reducing the complexity of manually piecing together information from multiple security tools.

Security Hub transforms correlated security signals into actionable insights through intuitive visualizations and contextual analytics, helping you identify critical patterns and trends and centralize security operations in your environment. For example, it detects and correlates scenarios where publicly exposed resources with highly exploitable vulnerabilities have access to storage with sensitive data. These insights provide enhanced risk context so you can make more informed decisions and take immediate action on security issues. Enhanced capabilities include exposure findings, security-focused asset inventory, attack path visualization, and automated response workflows with ticketing system integration. This centralized management enables streamlined remediation at scale while helping you minimize potential operational disruptions. 

For more information about AWS Regions where Security Hub is available, see the AWS Region table . You can enable Security Hub for individual accounts or across your entire AWS Organization with centralized deployment and management. The service integrates with existing AWS security capabilities including Amazon GuardDuty, Amazon Inspector, AWS Security Hub CSPM, and Amazon Macie, providing more comprehensive security posture without additional operational overhead.  

To learn more about the enhanced Security Hub and join the Preview, visit the AWS Security Hub console or the AWS Security Hub product page . 

AWS Network Firewall now offers active threat defense, a new security feature that helps you protect your Amazon Virtual Private Cloud (VPC) workloads against threat activities observed across AWS global infrastructure using Amazon threat intelligence.

AWS Network Firewall with active threat defense provides automated, intelligence-driven protection against dynamic, ongoing threat activities observed across AWS infrastructure. Once enabled, you can configure the managed rule group in your firewall policy to automatically block suspicious traffic, such as command-and-control (C2) communication, embedded URLs, and malicious domains. The feature provides protection by continuously updating rules based on current threat activity. AWS Network Firewall offers improved visibility for active threat defense rule group, allowing you to see indicator groups, types and threat names you’re protected against. If you are also an Amazon GuardDuty customer, related threat intelligence findings are marked with the threat list name “Amazon Active Threat Defense” going forward. These active threats can be automatically blocked by using the active threat defense managed rule group on AWS Network Firewall.

To get started with AWS Network Firewall with active threat defense, visit the AWS Network Firewall console or refer to our documentation . This feature is supported in all AWS Regions where AWS Network Firewall is available today, including the AWS GovCloud (US) Regions and China Regions. For more information about AWS Network Firewall and its features, please visit the AWS Network Firewall product page AWS Network Firewall .

Today, AWS Shield announces the preview of network security director, a new capability that provides visibility into the AWS resources in your network, identifies missing or misconfigured network security services, and recommends remediation steps. As threats continue to evolve, AWS Shield has expanded its capabilities beyond DDoS protection to help you easily identify resources requiring network and application protection and correctly secure them.

With network security director, AWS Shield helps you simplify network security management in three ways. First, it provides visibility into your network topology, which shows you the resources in your account and how they are connected to each other and the Internet. It discovers enabled AWS network security services, such as AWS WAF, VPC security groups, and VPC network access control lists (NACLs), and determines how well they are configured relative to AWS best practices and threat intelligence. Second, AWS Shield helps you quickly identify which missing or misconfigured firewalls require your immediate attention by showing you network security findings on your resources, prioritized by severity level.

Lastly, for each finding, you can view actionable remediation recommendations to correctly implement or update the configuration of the network security services you use.

Easily get answers, in natural language, to questions about your network security configurations from AWS Shield network security director within Amazon Q Developer in the AWS Management Console and chat applications. For example, you can ask “Are any of my Internet-facing resources vulnerable to DDoS?”, and Amazon Q shows relevant network security findings on specific resources with recommended remediation steps.This capability is available during preview at no additional cost in select AWS Regions: US East (N. Virginia) and Europe (Stockholm). Amazon Q Developer’s capability to analyze network security configurations is available in preview in US East (N. Virginia).

To learn more, visit the overview page.

Today, AWS announces further enhancements to Amazon GuardDuty Extended Threat Detection . This capability now includes coverage for multi-stage attacks targeting Amazon Elastic Kubernetes Service (EKS) clusters in your AWS environment. GuardDuty correlates multiple security signals across Amazon EKS audit logs, runtime behavior of processes, malware execution, and AWS API activity to detect sophisticated attack patterns that might otherwise go unnoticed.  These new attack sequence findings cover multiple resources and data sources over an extensive time period, allowing you to spend less time on first-level analysis and more time responding to critical severity threats, thereby minimizing business impact. 

GuardDuty Extended Threat Detection uses artificial intelligence and machine learning algorithms trained at AWS scale to automatically correlate security signals to detect critical threats. For example, it can identify an anomalous deployment of a privileged container followed by persistence attempts, crypto mining, and reverse shell creation, representing these related events as a single, critical-severity finding. You can then take action based on a new attack sequence finding type of critical severity. Each finding includes an incident summary, detailed events timeline, mapping to MITRE ATT&CK® tactics and techniques, and remediation recommendations.

This capability is automatically enabled for all GuardDuty customers at no additional cost in all Regions where GuardDuty is available. To detect attack sequences involving Amazon EKS clusters, you must enable GuardDuty EKS Protection, and GuardDuty recommends to also enable GuardDuty Runtime Monitoring for EKS for a more comprehensive security coverage. Take action on findings directly from the GuardDuty console or via integrations with AWS Security Hub and Amazon EventBridge.

To get started, visit the Amazon GuardDuty product page or try GuardDuty free for 30 days on the AWS Free Tier .

Today AWS Identity and Access Management (IAM) announced comprehensive multi-factor authentication (MFA) requirements for root users across all account types, with the expansion to member accounts. The new MFA enforcement marks a significant milestone in our ongoing commitment of secure by design principles, setting a high bar for our customers’ default security posture and building upon our previous security enhancements. Our security journey began with requiring MFA for AWS Organizations management account root users in May 2024, followed by expanding MFA requirements to standalone account root users in June 2024, and introducing centralized root access management for AWS Organizations in November 2024.

IAM helps you securely manage identities and control access to AWS services and resources. MFA is a security best practice in IAM that requires a second authentication factor in addition to the user name and password sign-in credentials. MFA is available at no additional cost and prevents over 99% of password-related attacks. You can use a range of supported IAM MFA methods, including FIDO-certified security keys to harden access to your AWS accounts. AWS supports FIDO2 passkeys for a user-friendly MFA implementation and allows customers to register up to 8 MFA devices per root and IAM user. For AWS Organizations customers, we recommend centralizing access account management through the management account and removing root user credentials from member accounts, which represents an even stronger security posture.

To learn more:

• Root user MFA guide
• Centrailzed root access

AWS Identity and Access Management (IAM) Access Analyzer now identifies who within your AWS organization has access to your Amazon S3, Amazon DynamoDB, or Amazon Relational Database Service (RDS) resources. It uses automated reasoning to evaluate all identity policies, resource policies, service control policies (SCPs), and resource control policies (RCPs) to surface all IAM users and roles that have access to your selected critical resources.

After the new internal access analyzer is enabled in the IAM console, the analyzer monitors your selected resources daily, and surfaces findings in a unified dashboard. The updated dashboard combines internal and external access findings to provide a 360-degree view of all access granted to your critical resources. Security teams can respond to new findings in two ways: taking immediate action to fix unintended access, or setting up automated notifications through Amazon EventBridge to engage development teams for remediation.

Internal access findings provide security teams the visibility to strengthen access controls on their critical resources and help compliance teams demonstrate access control audit requirements. Internal access findings are available in all AWS commercial Regions . To learn more about IAM Access Analyzer internal access findings:

• Read the AWS news blog post
• Review the pricing page
• Visit the IAM Access Analyzer documentation 

Introducing the updated AWS MSSP Competency (previously AWS Level 1 MSSP Competency) for partners with turn-key security solutions that transform how organizations approach cloud security. The update includes new categories to validate Partners’ security expertise in specific domains including Infrastructure Security, Workload Security, Application Security, Data Protection, Identity & Access Management, Incident Response, and Cyber Recovery. These categories validate service partners’ capabilities to deliver comprehensive security outcomes leveraging native AWS services and best-of-breed security tools.

Partners must meet core MSSP requirements and demonstrate expertise in at least one category through technical validation. Additionally, MSSP Competency Partners have the option to showcase how they integrate validated AWS Security Competency ISV solutions into their managed security services. This visibility helps AWS customers identify which MSSP Competency Partners can effectively manage their existing third-party security tools as part of a comprehensive security solution.

To learn more about AWS-validated fully managed security solutions, visit the AWS MSSP Competency page and contact a partner to evaluate your security needs.

Amazon CloudFront introduces a new console experience that simplifies the delivery of secure, high-performance applications to users on the internet. Setting up a content delivery network (CDN) traditionally required deep expertise in CDN configurations, domain management, and security best practices. The new CloudFront console experience streamlines this entire process with a unified approach to content delivery and security. The new experience automatically provisions and manages DNS records with Amazon Route 53 and TLS certificates with AWS Certificate Manager (ACM). Users can now create a secure, optimized distribution in as little as 30 seconds, regardless of their CDN expertise level.

When creating a distribution, CloudFront now automatically applies optimized settings based on your specific origin type. For example, when serving static websites from Amazon S3, CloudFront automatically configures Origin Access Control to prevent direct bucket access, optimizes caching settings for improved performance, and enables recommended security settings – all without requiring you to understand the underlying technical details of these components.

This new onboarding experience makes it easier for you to leverage AWS’ global edge network, reduce latency for your end users, and enhance the security posture of your applications. The new experience is available globally at no additional cost. To get started with the new CloudFront experience, visit the Amazon CloudFront console or check out our documentation .
 

AWS Certificate Manager (ACM) announces exportable public certificates that you can use on any workload that requires a public TLS certificate, whether within AWS or outside. With this release, you can issue public certificates that you can export and access the certificate’s private key to securely terminate TLS traffic on any compute workload. This includes EC2 instances, containers, or on-premises hosts.

ACM customers can now affordably issue, manage, and automate public certificates for use with your AWS, hybrid, or multicloud workloads. Previously, ACM-issued public certificates could only be used with integrated AWS services, such as Amazon CloudFront. Now, during certificate request, you can mark the certificate as exportable for use outside of integrated services as well. You can procure these certificates within seconds once you complete the required domain validation to prove that you are authorized to receive the certificate.

The exportable public certificates are valid for 395 days and costs $15 per FQDN and $149 per wildcard name. You don’t need to sign up for bulk issuance contracts and you only pay once for the lifetime of the certificate. Network and security administrators can monitor and automate the use of these certificates through ACM’s certificate lifecycle CloudWatch events

Security is top priority within AWS and your end users cannot export public certificates that were issued prior to this launch. AWS administrators can set IAM policies to authorize roles and users who can request exportable public certificates. The feature is available in all regions where ACM is available including the AWS GovCloud (US) and China Regions. Learn more about this feature here .