Researchers noted that they found several similar websites, two of which are still operating and require the same kind of behavior on behalf of the victim.
from darkreading https://ift.tt/ZkYq8VD
via IFTTT
Researchers noted that they found several similar websites, two of which are still operating and require the same kind of behavior on behalf of the victim.
from darkreading https://ift.tt/ZkYq8VD
via IFTTT
Today, we’re introducing the AWS Product Lifecycle page, a centralized resource that provides comprehensive information about service availability changes across AWS.
The new AWS Product Lifecycle page consolidates all service availability information in one convenient location. This dedicated resource offers detailed visibility into three key categories of changes: 1) services closing access to new customers, 2) services that have announced end of support, and 3) services that have reached their end of support date. For each service listed, you can access specific end-of-support dates, recommended migration paths, and links to relevant documentation, enabling more efficient planning for service transitions.
The AWS Product Lifecycle page helps you stay informed about changes that may affect your workloads and enables more efficient planning for service transitions. The centralized nature of this resource reduces the time and effort needed to track service lifecycle information, allowing you to focus more on your core business objectives and less on administrative overhead.
Today, you will find information on the new Product Lifecycle page about the services and capabilities availability updates summarized in the following paragraphs.
AWS service availability updates in 2025
After careful consideration, we’re announcing availability changes for a select group of AWS services and features. We understand that the decision to end support for a service or feature significantly impacts your operations. We approach such decisions only after thorough evaluation, and when end of support is necessary, we provide detailed guidance on available alternatives and comprehensive support for migration.
Services closing access to new customers
We’re closing access to new customers after June 20, 2025, for the following services or capabilities listed. Existing customers will be able to continue to use the service.
Services that have announced end of support
The following services will no longer be supported. To find out more about service specific end-of-support dates, as well as detailed migration information, please visit individual service documentation pages.
Services that have reached their end of support
The following services have reached their end of support date and can no longer be accessed:
The AWS Product Lifecycle page is available and all the changes described in this post are listed on the new page now. We recommend that you bookmark this page and check out What’s New with AWS? for upcoming AWS service availability updates. For more information about using this new resource, contact us or your usual AWS Support contacts for specific guidance on transitioning affected workloads.
from AWS News Blog https://ift.tt/bsaEw2S
via IFTTT
A threat actor known as Hazy Hawk has been observed hijacking abandoned cloud resources of high-profile organizations, including Amazon S3 buckets and Microsoft Azure endpoints, by leveraging misconfigurations in the Domain Name System (DNS) records.
The hijacked domains are then used to host URLs that direct users to scams and malware via traffic distribution systems (TDSes), according to
from The Hacker News https://ift.tt/9fSEl6v
via IFTTT
[Part 2 of 2 – Based on an interview with Zscaler CSO Deepen Desai]
By Holger Schulze, Cybersecurity Insiders
“Zero Trust isn’t a feature,” Deepen Desai told me during our RSA Conference interview. “It’s an architectural decision to stop trusting the network. You’re either enforcing that by design—or you’re pretending.”
In Part 1 of this series, we explored the failure of VPNs—how attackers exploit them, how they collapse under patching pressure, and how they expand risk instead of containing it. But our conversation in San Francisco didn’t stop at diagnosis. It turned toward what comes next.
The answer is Zero Trust. But not the watered-down, checkbox version.
“If your users connect and get placed on the network—even in the cloud—you’re not doing Zero Trust,” Desai said. “You’ve just moved your VPN to a new address.”
This isn’t about branding. It’s about architecture. And at Zscaler, that architecture is built on one foundational idea: attack surface reduction in the first place.
The Invisible Attack Surface
If the core flaw of VPNs is that they make applications reachable, then Zero Trust flips that completely. Desai described it as eliminating network presence altogether.
With Zscaler Private Access (ZPA), users never access the network. There is no IP assignment. No shared subnet. No inbound access to anything.
Instead, both users and applications establish outbound-only connections to the Zscaler Zero Trust Exchange. If identity, policy, and posture align, Zscaler stitches the user and app connections together.
“If you can scan the network, you’re on the network,” Desai said. “And if you’re on the network, the attacker can be too.”
This approach removes the need for VPN concentrators, inbound firewall rules, or exposed IPs. Applications go dark. And attackers can’t target what they can’t see.
The Philosophy That Replaces the Perimeter
At its core, Zero Trust is a framework built on three non-negotiable principles, defined by NIST and echoed in Zscaler’s architecture:
“Every one of those ideas breaks the legacy model,” Desai told me. “That’s why you can’t just rebrand your VPN and call it Zero Trust. It either enforces these tenets—or it doesn’t.”
At Zscaler, these principles are enforced not by firewalls, not by segmentation rules, but by the architecture itself. With ZPA, applications aren’t directly reachable, users aren’t on the network, and policies are enforced every time a connection is made.
From this foundation, the rollout begins.
The Four-Stage Shift to Zero Trust
Zscaler doesn’t advocate a forklift replacement of legacy systems. Instead, Desai laid out a four-stage adoption path—one that starts where the risk is highest and compounds benefit over time.
Before private apps, start with outbound traffic. Zscaler Internet Access (ZIA) enforces consistent policy and TLS inspection across all users—without backhauling traffic to a central datacenter.
This removes the need for on-prem proxies and applies protection close to the user. It’s the foundation that makes the rest of Zero Trust scalable.
The next move is to eliminate VPN tunnels altogether. ZPA makes private applications invisible to the internet—no public IPs, no exposed services, no inbound firewall rules.
“It’s not just blocking access,” Desai said. “It’s removing the ability to even knock on the door.”
Access is determined by who the user is, what device they’re using, and what policy allows. Not where they’re connecting from or what network they’re on.
This is where most organizations truly begin to understand the power of Zero Trust.
Instead of segmenting by subnet, VLAN, or NAC, Zscaler segments by user-to-app relationships. Policies are built around identity, not infrastructure. And Zscaler’s machine learning engine can detect real access patterns to suggest adaptive policies over time.
Desai shared one example where a customer believed they had 300 internal applications. Zscaler discovered over 10,000.
“You can’t segment what you don’t know exists,” he said. “But you also don’t have to do it all at once. Start with your crown jewels. Then isolate your riskiest users.”
That might include employees who routinely fail phishing simulations, users on unmanaged devices, or accounts showing anomalous behavior.
Even with segmentation in place, breaches happen. But Zero Trust doesn’t stop at prevention—it extends into containment.
Zscaler integrates deception directly into the access layer: decoy applications, seeded with breadcrumbs, are presented to users just like real apps. If touched, access to the real environment is immediately revoked—and the attacker is isolated.
“They don’t even know they’ve been shut out,” Desai said. “But they’ve already lost.”
This eliminates the lateral movement that VPNs so often enable—and turns the attacker’s playbook against them.
This is what makes Zero Trust more than prevention. It’s containment by design.
What Doesn’t Work: NAC and Cloud VPNs
Desai was unequivocal about what Zero Trust is not.
“Putting a VPN in the cloud doesn’t change what it does,” he told me. “If users still get placed on the network, you’ve changed the address, not the architecture.”
Network Access Control (NAC) solutions are equally limited. They may inspect device posture at the edge, but they can’t prevent what happens inside a session—especially if the attacker has valid credentials. They can’t block data exfiltration from within an approved connection. And they certainly can’t make applications invisible.
The Real Benefit: Simplicity That Scales
While the security benefits are clear, Desai pointed out that Zero Trust is also an operations win—especially for organizations struggling with VPN overhead.
According to the VPN Risk Report:
“It’s not just your security team that benefits,” Desai said. “It’s your IT team. It’s your users. It’s your CFO who doesn’t want to keep buying concentrators or renewing patching contracts.”
When infrastructure goes away, complexity and resulting cost follows it out the door.
Making the Case to the Board
Desai wrapped our conversation with advice for CISOs working to bring Zero Trust to the boardroom. His recommendation: don’t talk about controls. Talk about containment.
“The question isn’t whether you’ll be breached,” he said. “It’s what happens next. VPNs let that breach spread. Zero Trust stops it where it starts.”
With VPNs, the breach spreads. With Zero Trust, the breach is contained—access is limited by default, and even successful compromise can’t move laterally.
Desai advises CISOs to lead with these three points:
In a security climate where prevention is imperfect, containment is king.
A Shift That’s Already Happening
According to the 2025 VPN Risk Report, the transition is already happening. 65% of organizations are moving away from VPNs. 81% are investing in Zero Trust architecture.
This isn’t about buzzwords. It’s about control.
“VPNs make you reachable,” Desai said as we stood to leave. “Zero Trust makes your network and applications invisible to attackers. That’s the future.”
The post The End of VPNs — Part 2: Beyond the Buzz of Zero Trust first appeared on Cybersecurity Insiders.
The post The End of VPNs — Part 2: Beyond the Buzz of Zero Trust appeared first on Cybersecurity Insiders.
from Cybersecurity Insiders https://ift.tt/pDOtJMx
via IFTTT
High-pressure incidents can be defining moments for organizations, demanding immediate, coordinated, and often high-stakes responses. In the realm of cybersecurity, where threats evolve rapidly and stakes include sensitive data, reputational damage, and financial loss, the pressure to act quickly is intense. While technical tools and expertise often take center stage in incident response, an equally critical and sometimes underestimated component is effective communication. As leadership expert Simon Sinek famously said, “Leadership is not about being in charge. It is about taking care of those in your charge.” In the heat of a cyber crisis, that care manifests through structured, empathetic, and timely communication that aligns teams, reduces confusion, and drives action.
This article explores practical communication strategies drawn from real-world incident response experiences to help security teams navigate the complexities of an active cyber crisis with clarity, calm, and confidence.
The Role of Communication in Cybersecurity Incidents
In cybersecurity, high-pressure incidents frequently involve fast-moving and complex threats such as ransomware outbreaks, data breaches, supply chain compromises, or insider threats. Each minute during an incident counts, delays in containment can amplify damage exponentially. The ability to communicate clearly both within technical teams and with non-technical stakeholders is crucial to mitigating impact and accelerating recovery.
Consider the handling of the 2020 SolarWinds supply chain compromise, often cited as a textbook example of effective crisis communication in cybersecurity. The victim organization faced a highly sophisticated attack that silently compromised thousands of customers. Rather than resorting to silence or obfuscation, the company published transparent, technically detailed blog posts outlining what was known about the attack, how it was being investigated, and practical mitigations customers could apply. Alongside public communications, internal teams maintained continuous updates and alignment across engineering, security, and leadership functions. This dual internal-external communication approach helped build customer trust and enabled rapid adoption of defensive measures, containing the damage faster than might otherwise have been possible.
Done right, communication transforms incident response from a frantic scramble into a coordinated, focused effort where everyone understands their role, priorities, and next steps. It establishes a rhythm and clarity that reduces panic, eliminates duplicative work, and enable swift decision-making.
Key Elements of Effective Communication During an Incident
Effective communication can make or break an organization’s response to a cybersecurity incident. The following core practices have proven vital in maintaining clarity, control, and confidence during high-pressure moments:
a. Structured Communication Cadence
One of the first lessons is to establish a predictable rhythm for communications. When uncertainty and chaos abound, a set cadence of updates brings much-needed stability. For example, during a ransomware outbreak at a global manufacturing company, the response team instituted two-hourly technical syncs where engineers shared progress on containment and forensics. Meanwhile, a separate briefing for executives occurred every four hours, providing strategic context and business impact summaries. This predictable cadence ensured tactical teams and decision-makers were aligned, and no critical information fell through the cracks.
Choosing appropriate communication channels and intervals is essential. For example, chat platforms work well for rapid-fire technical updates, while email or video calls suit broader leadership briefings. The key is consistency; team members should know when and where to expect updates.
b. Audience-Centric Messaging
Another fundamental principle is tailoring communication to the audience’s needs. Not all stakeholders require or want the same level of technical detail. For instance, during a cloud misconfiguration incident that exposed customer data, the security engineers needed detailed packet captures and logs to identify root causes and patch vulnerabilities. Meanwhile, the executive board required a concise summary outlining the incident’s impact, legal obligations, and remediation timelines.
In a real-world scenario, a financial services company experienced a similar breach where technical teams worked around the clock analyzing system logs and firewall rules. Simultaneously, the C-suite received simplified updates focusing on risk exposure, regulatory reporting deadlines, and customer notification plans. This bifurcated communication approach prevented information overload for executives and ensured engineers had the detailed data they needed to act decisively.
Crafting messages with clarity and purpose for each audience helps avoid confusion, reduces unnecessary alarm, and builds trust. Technical teams value accuracy and completeness, while leadership prioritizes business risk and next steps. Separating these messages and customizing tone and depth helps keep everyone informed and aligned without overwhelming anyone.
c. Cross-Functional Coordination
Cyber incidents ripple beyond the technical realm. They affect legal compliance, public relations, human resources, and customer experience teams. In a recent phishing attack targeting a multinational’s workforce, the incident response team ensured early involvement of HR to notify affected employees and assist with password resets. Legal counsel was looped in promptly to assess breach notification requirements under GDPR. Meanwhile, communications teams prepared customer-facing statements to manage external reputation.
Such cross-functional integration avoids conflicting messages, ensures regulatory compliance, and fosters a unified organizational response. Predefined roles and communication pathways, documented well before incidents occur, enable this coordination to happen smoothly under pressure.
d. Clear Escalation Paths
Time is the most precious resource during a cyber crisis, and ambiguity about decision-making authority can cost valuable minutes or hours. In one incident involving suspected data exfiltration, lack of a clear escalation matrix caused a six-hour delay before containment approvals were obtained. This delay extended the exposure window and increased damage.
Following that event, the company implemented a role-based decision tree that clearly defines who can authorize containment actions, legal escalations, or public disclosures at each incident severity level. This clarity reduced response latency in subsequent drills and real incidents alike, emphasizing the importance of predefined escalation paths in the communication plan.
e. Calm, Concise Communication Style
How information is communicated during a crisis influences team morale and effectiveness as much as what is communicated. During a distributed denial-of-service (DDoS) attack on a major retail platform, the incident commander kept all updates short, factual, and evenly toned, avoiding panic-inducing language. This steady tone helped the engineering teams remain focused on mitigation efforts without distraction, while leadership maintained a clear understanding of progress.
Training teams to communicate calmly and assertively rather than reactively or emotionally can significantly improve performance under pressure. Consistent messaging with a measured tone reduces misunderstandings and builds confidence in the response process.
Recap Putting Communication into Practice
To illustrate these principles, consider a mid-sized financial services company responding to a ransomware infection:
Structured Cadence: The incident manager set up hourly updates via group chat for technical responders, while business leaders received consolidated briefings every four hours via video conference.
Audience-Centric Messaging: Technical teams received detailed logs and mitigation steps, while executives got high-level summaries focusing on customer impact and regulatory notifications.
Cross-Functional Coordination: Legal and compliance teams joined briefings to advise on breach reporting timelines; customer support prepared scripts for incoming inquiries; HR alerted and supported affected employees.
Clear Escalation Paths: Predefined roles ensured that authorization for network isolation and public communications moved quickly from technical leads to CISO and then CEO without delay.
Calm, Concise Style: Incident communications remained steady and factual, avoiding speculation or alarmist language, which helped maintain team focus and stakeholder confidence.
This integrated communication approach allowed the company to contain the attack within 24 hours, minimize business disruption, and meet all regulatory obligations on time.
Conclusion
Senior engineering leaders must recognize that communication is as vital as the technical response during incidents. Clear, timely, and targeted communication helps contain threats, reduces confusion, and enhances decision-making. Structured updates, predefined escalation paths, and cross-functional alignment transform chaos into coordinated action. The tone and clarity set by leaders directly influence team performance under pressure. Communication is infrastructure, not just support, and must be woven into incident response plans to safeguard systems and maintain organizational trust.
The post Engineering Calm in Crisis: Lessons from the Frontlines of Security first appeared on Cybersecurity Insiders.
The post Engineering Calm in Crisis: Lessons from the Frontlines of Security appeared first on Cybersecurity Insiders.
from Cybersecurity Insiders https://ift.tt/SeHnrcN
via IFTTT
In 2024, browser security faced some of the most advanced cyber threats to-date. As enterprises continue to transition to and from remote work environments, relying on SaaS platforms, cloud-based applications, hybrid work setups, and BYOD policies, attackers have become hyperfocused on the browser as the connective tissue linking and supporting almost all work and personal activities.
The rise of AI-powered attacks, abusive cloud hosting services, phishing-as-a-service (PhaaS), and zero-day vulnerabilities that focus on enterprise browsers have underscored the need for a new approach to browser security. Traditional network and endpoint security tools alone are no longer enough. Menlo Security’s annual “State of Browser Security Report” reveals a significant surge in browser-based attacks, particularly those utilizing artificial intelligence (AI) and sophisticated impersonation methods.
Key Research Findings
The modern browser transcends its traditional role as a web access tool; it’s now a primary entry vector for advanced cyberattacks. Attackers are increasingly leveraging browser vulnerabilities to pilfer sensitive data and circumvent conventional security measures. Menlo researchers identified a dramatic 140% surge in browser-based phishing attacks year-over-year, coupled with a 130% increase in zero-hour phishing incidents specifically.
Credential phishing continued to run rampant in 2024, largely because traditional security measures like firewalls, secure web gateways, and antivirus tools remain ineffective against these, and other sophisticated techniques used by cybercriminals. In fact, six days is the average window of exposure before legacy security tools can detect threats from zero-hour phishing attacks. While many enterprises have endeavored to improve browser security, they tend to focus on security at the network or endpoint level, which are not equipped to combat evasive threats like obfuscating malicious code, fileless malware and memory-only payloads. These techniques hide malicious activity within seemingly legitimate web traffic, making detection more difficult.
Cloud-network services have attempted to mitigate the growing problem of browser-based attacks, but they often introduce added complexity and significant management costs without delivering robust protection against advanced phishing tactics. Compounding these challenges is the escalating trend of attackers exploiting cloud services themselves to host malicious content, including phishing sites and ransomware. Notably, AWS and CloudFlare accounted for nearly 50% of all instances of abused cloud hosting in 2024. This concentration underscores the allure of major cloud providers as targets for malicious actors who seek to leverage their extensive infrastructure for illicit activities, highlighting a critical security gap that existing solutions are failing to adequately address.
Continuing Trends
The data in the Menlo State of Browser Security Report is a clear indication of the current threat landscape, and what enterprises can expect in 2025 and beyond. Here are our research-based predictions for the months to come:
1.Ransomware will continue to reign supreme. Ransomware will remain a highly prolific attack type, with cybercriminals targeting critical infrastructure to extract financial gains. We expect threat actors to increasingly use browser-based attacks to deploy ransomware, targeting sectors like healthcare, energy and transportation, and using the advanced techniques described above to bypass traditional defenses. The significant impact of ransomware attacks, such as the phishing campaign against Change Healthcare in 2024, highlights the need for organizations to prioritize browser security, adopt strong security measures and stay updated with the latest threat intelligence and business continuity protocols.
2.AI-driven deepfakes will aid in bypassing traditional security tools. The volume of AI-driven cyber fraud has not yet reached its peak – we will see this attack type continue to rise in 2025 and beyond. Scam activities such as fake AI tools posing as legitimate platforms offering premium AI services will be used to steal login credentials and personal data, or direct users to phishing forms. Exploitation of user trust through sophisticated social engineering techniques will be key to targeting social media platforms and search engines.
3.The cyber gap between small and large businesses will continue, leaving smaller businesses more vulnerable to attack. Larger enterprises are among the first to begin incorporating browser security strategies and security tooling that incorporates AI, helping with defenses that leave too much room for human error. On the other hand, we will see a larger proportion of small businesses continue to be affected by ransomware and other browser-based threats due to fewer resources, lack of dynamic security controls in the browser, and their inability to effectively monitor user behavior. Organizations will also start to leverage AI to level out their Security Operations Centers (SOCs), so that they don’t need as many resources to run it. Regardless of size, browser security is no longer optional but a fundamental survival strategy requiring proactive protection and preventative security.
4.Threats to edge and IoT devices will rise. Edge and Internet of Things (IoT) devices are becoming prime targets for cybercriminals, particularly due to their often-limited security measures and widespread use in both personal and corporate settings. From smart cameras and wearables to home assistants, there will be more zero-day vulnerabilities exploited in the wild, with threat actors identifying and exploiting these weaknesses to gain control of these devices, use them for DDoS attacks and other malicious activities.
5.Left unsecured, remote and hybrid environments will exacerbate insider threats. In the months to come, insider threats will increasingly originate from well-intentioned users who fall victim to sophisticated targeted attacks, exacerbated by remote and hybrid work environments. New tools and technologies will emerge to assist users in avoiding these risks, removing the burden of identifying and mitigating potential risks on their own. These tools will be able to detect malicious activity and perform far above the capacity of manual human analysis.
Browser security will remain a critical area of focus for both security teams and end users, affecting both equally. The cyber threat landscape is shifting quickly, driven by advancements in technology such as AI and also changes in how and where people work. Cybercriminals are constantly refining their attack tactics – organizations must be doing the same on the defensive side, looking to implement robust security measures, prioritizing browser safety, and leveraging innovative tools to detect and thwart threats.
The post Recent Evolution of Browser-based Cyber Threats, and What to Expect Next first appeared on Cybersecurity Insiders.
The post Recent Evolution of Browser-based Cyber Threats, and What to Expect Next appeared first on Cybersecurity Insiders.
from Cybersecurity Insiders https://ift.tt/59gpdTR
via IFTTT
I want to introduce the AWS Cloud Infrastructure Day to provide a comprehensive showcase of latest innovations in AWS cloud infrastructure. This event will highlight cutting-edge advances across compute, artificial intelligence and machine learning (AI/ML), storage solutions, networking capabilities, serverless, and accelerated technologies, and global infrastructure.
Join us for AWS Cloud Infrastructure Day, a free-to-attend one-day virtual event on May 22, 2025, starting at 11:00 AM PDT (2:00 PM EDT). We will stream the event simultaneously across multiple platforms, including LinkedIn Live, Twitter, YouTube, and Twitch.

Here are some of the highlights you can expect from this event:
Willem Visser, VP of EC2 Technology will open with the introduction of the AWS journey since 2006, when Amazon Elastic Compute Cloud (Amazon EC2) was launched with the goal of customer-obsessed innovation. He will speak about the progress made over nearly two decades in cloud infrastructure to support both startups and enterprise workloads based on scale, capacity, and flexibility.
You can learn how AWS developed beyond computing instances to create a complete cloud infrastructure, including the parallel evolution of services like storage and networking capabilities.
Todd Kennedy, Principal Engineer, GoDaddy, will share GoDaddy’s Graviton adoption journey and the benefits it reaped from Graviton. Todd will walk through an example to demonstrate moving Rust workloads to Graviton. Learn how GoDaddy achieved 40 percent compute cost savings and over 20 percent performance gains.
This event covers a variety of topics related to AWS Cloud infrastructure. Here are interesting topics that caught my interest:
This event is perfect for technical decision-makers and developers and offers deep technical insights and hands-on demonstrations of the latest AWS Cloud infrastructure solutions.
To learn more details, review the event schedule and register for AWS Cloud Infrastructure Day.
— Channy
How is the News Blog doing? Take this 1 minute survey!
(This survey is hosted by an external company. AWS handles your information as described in the AWS Privacy Notice. AWS will own the data gathered via this survey and will not share the information collected with survey respondents.)
from AWS News Blog https://ift.tt/ZyoprY8
via IFTTT
When running container workloads, you need to understand how software vulnerabilities create security risks for your resources. Until now, you could identify vulnerabilities in your Amazon Elastic Container Registry (Amazon ECR) images, but couldn’t determine if these images were active in containers or track their usage. With no visibility if these images were being used on running clusters, you had limited ability to prioritize fixes based on actual deployment and usage patterns.
Starting today, Amazon Inspector offers two new features that enhance vulnerability management, giving you a more comprehensive view of your container images. First, Amazon Inspector now maps Amazon ECR images to running containers, enabling security teams to prioritize vulnerabilities based on containers currently running in your environment. With these new capabilities, you can analyze vulnerabilities in your Amazon ECR images and prioritize findings based on whether they are currently running and when they last ran in your container environment. Additionally, you can see the cluster Amazon Resource Name (ARN), number EKS pods or ECS tasks where an image is deployed, helping you prioritize fixes based on usage and severity.
Second, we’re extending vulnerability scanning support to minimal base images including scratch, distroless, and Chainguard images, and extending support for additional ecosystems including Go toolchain, Oracle JDK & JRE, Amazon Corretto, Apache Tomcat, Apache httpd, WordPress (core, themes, plugins), and Puppeteer, helping teams maintain robust security even in highly optimized container environments.
Through continual monitoring and tracking of images running on containers, Amazon Inspector helps teams identify which container images are actively running in their environment and where they’re deployed, detecting Amazon ECR images running on containers in Amazon Elastic Container Service (Amazon ECS) and Amazon Elastic Kubernetes Service (Amazon EKS), and any associated vulnerabilities. This solution supports teams managing Amazon ECR images across single AWS accounts, cross-account scenarios, and AWS Organizations with delegated administrator capabilities, enabling centralized vulnerability management based on container images running patterns.
Let’s see it in action
Amazon ECR image scanning helps identify vulnerabilities in your container images through enhanced scanning, which integrates with Amazon Inspector to provide automated, continual scanning of your repositories. To use this new feature you have to enable enhanced scanning through the Amazon ECR console, you can do it by following the steps in the Configuring enhanced scanning for images in Amazon ECR documentation page. I already have Amazon ECR enhanced scanning, so I don’t have to do any action.
In the Amazon Inspector console, I navigate to General settings and select ECR scanning settings from the navigation panel. Here, I can configure the new Image re-scan mode settings by choosing between Last in-use date and Last pull date. I leave it as it is by default with Last in-use date and set the Image last in use date to 14 days. These settings make it so that Inspector monitors my images based on when they were running in the last 14 days in my Amazon ECS or Amazon EKS environments. After applying these settings, Amazon Inspector starts tracking information about images running on containers and incorporating it into vulnerability findings, helping me focus on images actively running in containers in my environment.

After it’s configured, I can view information about images running on containers in the Details menu, where I can see last in-use and pull dates, along with EKS pods or ECS tasks count.

When selecting the number of Deployed ECS Tasks/EKS Pods, I can see the cluster ARN, last use dates, and Type for each image.

For cross-account visibility demonstration, I have a repository with EKS pods deployed in two accounts. In the Resources coverage menu, I navigate to Container repositories, select my repository name and choose the Image tag. As before, I can see the number of deployed EKS pods/ECS tasks.
When I select the number of deployed EKS pods/ECS tasks, I can see that it is running in a different account.

In the Findings menu, I can review any vulnerabilities, and by selecting one, I can find the Last in use date and Deployed ECS Tasks/EKS Pods involved in the vulnerability under Resource affected data, helping me prioritize remediation based on actual usage.

In the All Findings menu, you can now search for vulnerabilities within account management, using filters such as Account ID, Image in use count and Image last in use at.
![]() |
![]() |
|---|
Key features and considerations
Monitoring based on container image lifecycle – Amazon Inspector now determines image activity based on: image push date ranging duration 14, 30, 60, 90, or 180 days or lifetime, image pull date from 14, 30, 60, 90, or 180 days, stopped duration from never to 14, 30, 60, 90, or 180 days and status of image running on the container. This flexibility lets organizations tailor their monitoring strategy based on actual container image usage rather than only repository events. For Amazon EKS and Amazon ECS workloads, last in use, push and pull duration are set to 14 days, which is now the default for new customers.
Image runtime-aware finding details – To help prioritize remediation efforts, each finding in Amazon Inspector now includes the lastInUseAt date and InUseCount, indicating when an image was last running on the containers and the number of deployed EKS pods/ ECS tasks currently using it. Amazon Inspector monitors both Amazon ECR last pull date data and images running on Amazon ECS tasks or Amazon EKS pods container data for all accounts, updating this information at least once daily. Amazon Inspector integrates these details into all findings reports and seamlessly works with Amazon EventBridge. You can filter findings based on the lastInUseAt field using rolling window or fixed range options, and you can filter images based on their last running date within the last 14, 30, 60, or 90 days.
Comprehensive security coverage – Amazon Inspector now provides unified vulnerability assessments for both traditional Linux distributions and minimal base images including scratch, distroless, and Chainguard images through a single service. This extended coverage eliminates the need for multiple scanning solutions while maintaining robust security practices across your entire container ecosystem, from traditional distributions to highly optimized container environments. The service streamlines security operations by providing comprehensive vulnerability management through a centralized platform, enabling efficient assessment of all container types.
Enhanced cross-account visibility – Security management across single accounts, cross-account setups, and AWS Organizations is now supported through delegated administrator capabilities. Amazon Inspector shares images running on container information within the same organization, which is particularly valuable for accounts maintaining golden image repositories. Amazon Inspector provides all ARNs for Amazon EKS and Amazon ECS clusters where images are running, if the resource belongs to the account with an API, providing comprehensive visibility across multiple AWS accounts. The system updates deployed EKS pods or ECS tasks information at least one time daily and automatically maintains accuracy as accounts join or leave the organization.
Availability and pricing – The new container mapping capabilities are available now in all AWS Regions where Amazon Inspector is offered at no additional cost. To get started, visit the AWS Inspector documentation. For pricing details and Regional availability, refer to the AWS Inspector pricing page.
PS: Writing a blog post at AWS is always a team effort, even when you see only one name under the post title. In this case, I want to thank Nirali Desai, for her generous help with technical guidance, and expertise, which made this overview possible and comprehensive.
— Eli
How is the News Blog doing? Take this 1 minute survey!
(This survey is hosted by an external company. AWS handles your information as described in the AWS Privacy Notice. AWS will own the data gathered via this survey and will not share the information collected with survey respondents.)
from AWS News Blog https://ift.tt/LWh9fGP
via IFTTT
Many events are taking place in this period! Last week I was at the AI Week in Italy. This week I’ll be in Zurich for the AWS Community Day – Switzerland. On May 22, you can join us remotely for AWS Cloud Infrastructure Day to learn about cutting-edge advances across compute, AI/ML, storage, networking, serverless technologies, and global infrastructure. Look for events near you for an opportunity to share your knowledge and learn from others.
What got me particularly excited last Friday was the introduction of Strands Agents, an open source SDK that you can use to build and run AI agents in just a few lines of code. It can scale from simple to complex use cases, including local development and production deployment. By default, it uses Amazon Bedrock as model provider, but many others are supported, including Ollama (to run models locally), Anthropic, Llama API, and LiteLLM (to provide a unified interface for other providers such as Mistral). With Strands, you can use any Python function as a tool for your agent with the @tool decorator. Strands provides many example tools for manipulating files, making API requests, and interacting with AWS APIs. You can also choose from thousands of published Model Context Protocol (MCP) servers, including this suite of specialized MCP servers that help you get the most out of AWS. Multiple teams at AWS already use Strands for their AI agents in production, including Amazon Q Developer, AWS Glue, and VPC Reachability Analyzer. Read it all in Clare’s post.
Last week’s launches
Here are the other launches that got my attention:
Additional updates
Here are some additional projects, blog posts, and news items that you might find interesting:


Upcoming AWS events
Check your calendars and sign up for these upcoming AWS events:
That’s all for this week. Check back next Monday for another Weekly Roundup!
– Danilo
from AWS News Blog https://ift.tt/c762jsw
via IFTTT
As a website owner, one of my top priorities is to ensure that my website is protected from cyber threats. After trying various web application firewalls (WAFs), I recently discovered SafeLine WAF, and I’m thoroughly impressed. If you’re looking for an affordable, yet powerful WAF solution, SafeLine is the perfect choice.
What is SafeLine WAF?
SafeLine WAF is a web application firewall designed to protect websites from a variety of attacks, including SQL injections, cross-site scripting (XSS), and zero-day attacks. It acts as a shield between your website and malicious traffic, ensuring that your website remains secure while still allowing legitimate users to interact with your site.
How SafeLine Works
What sets SafeLine apart from other WAF solutions is its semantic analysis engine, which goes beyond traditional signature-based detection. Instead of just identifying known attack patterns, SafeLine analyzes the behavior and context of incoming traffic to detect even sophisticated, zero-day attacks. This makes it not only effective but also highly adaptable to evolving threats.
Key Features of SafeLine WAF
1.Semantic Analysis for Advanced Threat Detection
SafeLine’s semantic analysis engine sets it apart from other WAFs. Unlike traditional signature-based firewalls that can only detect known threats, SafeLine looks at the behavior and context of traffic, enabling it to detect sophisticated attacks that are not yet widely recognized. This means your website is protected from both known and unknown threats.
2.Bot Protection
SafeLine provides multi-layered defense against bot attacks like malicious crawlers through CAPTCHA verification, dynamic protection, and anti-replay protection.
3.HTTP Flood DDoS Protection
The most common way to defend against HTTP flood DDoS attacks is to limit the rate of visits from source IPs. But it’s not enough. Skilled attackers will find ways to bypass detection. Therefore, in addition to rate limiting, SafeLine also supports Waiting Room, to limit user traffic.
4.Identity and Access Management
SafeLine provides unified identity management for both on-premise and cloud applications through standard protocols.
5.Customizable Security Rules
SafeLine provides the ability to customize security rules based on your specific needs. Whether it’s blocking certain types of traffic or monitoring suspicious activity, you can fine-tune the firewall to provide the exact level of protection your website needs.
6.User-Friendly Setup and Management
Not only is SafeLine one of the most affordable WAF solutions, but it is also incredibly easy to use. The setup process is fast and straightforward, making it perfect for those who don’t have extensive technical knowledge.
Once installed, the intuitive dashboard (See SafeLine Demo here) makes managing and monitoring your website’s security effortless. You can easily access attack logs, view real-time alerts, and make custom adjustments without a steep learning curve.
Why SafeLine is the Best Choice for Small Businesses
When it comes to WAFs, price can often be a limiting factor, especially for small businesses or personal websites. Many high-quality WAFs can cost hundreds of dollars per month, making them inaccessible to those with limited budgets.
However, SafeLine is a game-changer in this regard. It provides a Free edition for personal use. The Lite edition costs $10 per month. For users needing more advanced features, the Pro edition is also available at a competitive price of $100 per month, giving you full flexibility and powerful protection.
The key takeaway here is that SafeLine offers the best value for the features it provides. Whether we’re a small business, an individual site owner, or an enterprise, SafeLine is here to keep our websites safe from cyber threats.
The post SafeLine WAF: Best Security Choice for Small Businesses first appeared on Cybersecurity Insiders.
The post SafeLine WAF: Best Security Choice for Small Businesses appeared first on Cybersecurity Insiders.
from Cybersecurity Insiders https://ift.tt/z5lp08b
via IFTTT