Check out the Largest Integration Ecosystem in Cybersecurity and IT and request to be included. 

Synqly Adds AWS Network Security Integration for Cloud Traffic Visibility

Synqly’s Network Security Unified API now supports AWS Network Security. Security vendors building on Synqly can connect directly to AWS network traffic data and give their OEM customers visibility into traffic across AWS environments, without carrying the engineering cost of a custom log pipeline built and maintained in house. For product and engineering teams already juggling several cloud providers inside a single customer base, this is one more piece of coverage they no longer have to build themselves.

What is AWS Network Security?

AWS Network Security is the traffic-monitoring capability built into Amazon Web Services, surfaced most visibly through VPC Flow Logs. VPC Flow Logs capture both accepted and rejected traffic at the network interface level, so a security team can see not only what got through a network path but also what was blocked. That interface-level detail is what separates a genuinely useful network security signal from a summarized report that arrives too late to act on.

Organizations running production workloads on AWS rely on this data to catch lateral movement inside a VPC, spot early signs of data exfiltration, and flag network paths that were misconfigured during a deployment.

For the full picture of the platform itself, visit the AWS website.

What OEM Customers Can Do with the AWS Network Security Integration

With the integration live, OEM customers building on Synqly can query traffic events and pull traffic log configurations from a customer’s AWS environment through one consistent API, instead of writing and maintaining a bespoke AWS connector. The connector exposes two capabilities:

Capability What it does
Query traffic events Returns AWS network activity normalized to the OCSF Network Activity class (class_uid 4001), so a vendor’s existing detection logic consumes AWS traffic the same way it consumes traffic from any other Synqly provider.
Query traffic log configurations Discovers which flow log configurations already exist in a customer’s AWS account before pulling data, which shortens onboarding and removes the guesswork of standing up a new cloud integration.

The normalization step matters more than it sounds. Because AWS traffic arrives in the OCSF Network Activity schema, a product team does not have to write separate parsing logic every time it adds a cloud provider. Taken together, these two capabilities give security products the raw material to build detections for lateral movement, exfiltration, and misconfigured network paths across AWS infrastructure, without asking an engineering team to reverse-engineer AWS’s own logging formats first.

Full configuration and setup instructions live in the AWS Network Security Configuration Guide on the Synqly documentation site.

How This Fits Synqly’s Existing AWS Coverage

This integration extends AWS’s footprint inside the Synqly ecosystem rather than introducing AWS for the first time. Synqly customers already connect to AWS through cloud security and identity integrations, and this AWS network security integration adds a third category of AWS coverage. Each one stands on its own, so the pages above cover their respective use cases in full.

How the Network Security Unified API Works

This AWS network security integration is part of Synqly’s Network Security Unified API, which is built around a simple problem. Most OEM security vendors need to support every major cloud provider a customer might run on, and building that support one integration at a time is slow and expensive to maintain as each provider changes its logging formats over time.

Instead of standing up and maintaining separate connections to AWS, Google Cloud, and Microsoft Azure on their own, product teams integrate with Synqly once and pick up new providers, including this AWS network security integration, as Synqly adds them. For a team weighing whether to build these connectors in house or bring in a partner, that difference shows up directly on the roadmap: less time spent on plumbing, and more time spent on the detection and response features that actually differentiate a security product.

Where to Find More Details

Full details on the AWS network security integration, including supported capabilities and schema mappings, live on the AWS Network Security integration partner page. For hands-on setup, the AWS Network Security Configuration Guide walks through provider configuration from start to finish. A full list of every live integration is maintained on the Synqly integrations page.

https://www.synqly.com

Steve brings a proven track record of turning complex technical challenges into scalable, user-centric products. Drawing on his experience leading engineering organizations at Styra, Illumio, and Juniper Networks, Steve shares his insights on product innovation, cloud-native security, and modernizing cybersecurity solutions. He is dedicated to building high-performing teams to fix the broken state of security integrations.


  • Platform
  • Integrations
  • Resources
  • About
  • Blog