Noname Security Platform Updates: 3.24 Release
Akamai acquired Noname Security in June 2024. The Noname Security product is now Akamai API Security, but this archived blog post reflects the product and feature names on the original date of publication.
We are excited to provide the latest news and features about the Noname Security platform. These features help you protect your APIs from a broader range of attacks, improve your security posture, and simplify your API security operations.
In this blog post, we’ll dive into the latest updates that will redefine how you interact with our product across the four pillars — Runtime Security, Discovery, Posture Management, and Active Testing.
Expanded resource connection status view
The Noname Security platform can now support connection status view for resources discovered through NGINX, MuleSoft, Apigee, F5, and Kong integrations. Previously, resource connection status was available for cloud resources hosted on AWS and Azure. Now, you can capture the connection status and additional attributes for resources connected to the Noname Security platform through API Gateway and Load Balancer integrations. This lets you quickly determine which resources send traffic to your Noname platform, and identify failed connections or disconnected resources.
For example, you can now see if a server discovered through your NGINX integration is still online and double-check its NGINX version. You can also see details for applications connected to your MuleSoft instance, including traffic sent to the Noname platform over the last 24 hours, application versions, and environments in which apps are deployed. The attributes discovered by this feature are automatically populated in your Inventory view to make monitoring and troubleshooting your environment easier.
Connection status for NGINX resources
To learn more about this feature, please visit the Traffic Sources documentation.
Traffic Audit (Private Preview)
Traffic Audit is a new capability of the Noname Security platform that allows you to record, visualize, and analyze API traffic in your environment. Once enabled, Traffic Audit records API data flows that match specific criteria across your application environments, including typical and anomalous API activity. This makes it easier for you to discover and manage the risk exposure of suspicious users and unusual API behaviors. Each Traffic Audit can be custom-tailored to your particular use case, allowing you to capture and retain traffic according to predetermined filters and rules.
For example, you can create a Traffic Audit for all APIs captured by the Noname Security platform that contain personally identifiable information and originate outside your corporate IP range. The resulting information can be used to perform forensic analysis for specific attacks, investigate suspicious user behavior, or troubleshoot your API configurations.
Sample Traffic Audit result
In addition, Traffic Audit includes granular search and filtering capabilities. This allows you to hone in on particular data flows, assess specific API behavior, and create incidents based on traffic patterns. For instance, after addressing a known API vulnerability, you can perform a highly targeted Traffic Audit to validate the resolution or identify additional APIs that need your attention.
The Traffic Audit feature is currently in Private Preview. Please contact your Noname Security account representative to learn more about enabling Traffic Audit capability in your environment.
Remote telemetry configuration
With this release, we add the flexibility to granularly control the Noname Telemetry Service permissions directly within the Noname platform user interface. The Noname Telemetry Service, an optional capability for both software as a service (SaaS) and on-premises Noname Security deployments, allows the Noname support team to monitor system health remotely.
When enabled, the Telemetry Service automatically and securely collects essential system information necessary for monitoring the health of your servers. It also generates support cases when system metrics exceed expected levels. This significantly reduces support resolution times and allows Noname to address reliability issues with your deployment proactively.
The Support Settings page updated in this release now provides a transparent view into the current state of the Telemetry Service configuration, enables you to opt in or out of all system monitoring services, and includes controls for turning extra support services on or off.
The new Support Settings user interface for on-prem deployments
To learn more about the Noname Telemetry Service, please visit the Noname Documentation site.
For additional information about the Noname Security 3.24 release, please review the release notes.