Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Traditionally, securing APIs in AWS has involved a frustrating trade-off. Obtaining a full view of your API Fabric requires weeks or months of deploying various agents, setting up traffic analysis, and enduring lengthy professional services engagements. The outcome? An unacceptably slow time-to-value that keeps you unaware of potential risks for too long. The main issue hasn't only been locating APIs, but also the extensive wait to identify them. But what if that trade-off is no longer necessary?

In enterprise IT, there’s a familiar story: moving applications to the cloud is easy—but securely connecting cloud workloads isn’t. Cloud migration is no longer a question of if, but how fast enterprises can make the shift. As of 2025, an estimated 67% of enterprise infrastructure runs in the cloud, highlighting the widespread adoption of cloud hosting and infrastructure services worldwide.

Today at re:Inforce Amazon Web Services (AWS), unveiled an enhanced version of AWS Security Hub which will enable organizations to surface and prioritize active risks in their cloud environment. Security Hub transforms security signals into actionable insights and offers intuitive visualizations and natural language summaries. Tines will offer workflow orchestration and automation for this enhanced version of Security Hub.

As quantum computing creeps closer, the cryptographic mechanisms on which today’s digital world relies are becoming more and more fragile. In a prescient move, AWS Key Management Service (KMS) now supports ML-DSA, one of the first post-quantum digital signatures, which has become a standard under FIPS 203. This is an important step in AWS’s broader efforts to prepare customers for the post-quantum secure future.

At Tines, we rely heavily on AWS Elastic Container Service (ECS) to power our workflow automation platform. For a couple of years, we used Fargate as our default compute layer – offering simplicity and removing the need to manage underlying hosts. However, as we scaled, we started hitting the edges of what Fargate could reliably offer. This is the story of why we migrated our backend services to an EC2-backed ECS Capacity Provider and what we learned along the way.

Today, we’ve announced during AWS re:Inforce 2025 that Cato Networks has received the “Deployed on AWS” badge, which identifies Amazon Web Services (AWS) partners whose products are powered by AWS infrastructure. As a Leader in the 2024 Gartner Magic Quadrant for Single-Vendor SASE, Cato sets the standard for converging networking and security in a single, cloud-native platform.

On June 12, 2025, a global outage at Google Cloud Platform (GCP) brought critical infrastructure to a halt. The ripple effects were immediate. Services from Palo Alto Networks and Cloudflare—both of which rely on GCP—experienced outages that lasted hours. Enterprises depending on these services were left blind and exposed. This wasn’t a first. It won’t be the last. But it was a wake-up call. When SASE, SSE, or SD-WAN platforms go down, the business is down. Productivity stalls.

A new integration between 1Password and AWS Secrets Manager makes it faster and easier to sync secrets across environments – all from within the 1Password desktop app. This update enables all 1Password and AWS Secrets Manager joint customers to simply and securely deliver secrets to AWS Secrets Manager. It’s the fast, familiar 1Password experience you know and trust – now extended to include environment variables and secrets support.

1Password has signed a strategic collaboration agreement (SCA) with AWS to help modern enterprises close security blind spots, accelerate secure cloud adoption, and manage access in increasingly complex hybrid and AI-driven environments. This collaboration represents a long-term commitment to co-innovation, global growth, and enabling the adoption of AI tools, all while expanding support for the shared customers of 1Password and AWS.