Version 1.7
Release Date: March, 2025
Last updated
Release Date: March, 2025
Last updated
Version 1.7 of Atlas, the Netacea customer portal is here.
As well as populating Quarantine with specific items, Netacea can also provide matches that are based on matching patterns across multiple headers within the incoming requests, allowing Netacea to effective defend against attackers who continuously modify headers to attempt to bypass detection. These are grouped under the heading Complex Patterns.
You can now see all Complex Patterns that are applied to a datastream by clicking the Complex Patterns stat on your Quarantine page, just click again to go back to the quarantined items list.
These patterns instantly detect and block attackers when they use known malicious behaviour, such as using a non-ASCII character in the user agent that to the human eye reads just like a standard ASCII alphabet letter.
Now when searching for an item in the Quarantine area of the Portal you can see if an attacker matching your search query would have triggered protection via a complex pattern used on your datastream even if there hasn’t been an attack of that nature.
When reviewing an attacker fingerprint on the Details/More Info page you will now see if the value you are investigating is caught by a Complex Pattern, or by a Known Attack Signal (KAS) list that your datastream is subscribed to. For more info on Known Attack Signal (KAS) lists that you are subscribed to you can go to the settings for your datastream.
To improve user experience, The Top Attack Sources table has been given it’s own page under Response, and now is no longer limited to 10, allowing you to view the top 100 attack sources on a your datastreams for any dimension and see the reason why we blocked that traffic.
Additionally the dashboard navigation has been simplified, to reduce clutter on your page.
There is now information about robots.txt compliance on the Known Bots Dashboard! With these two new fields you can infer whether or not a self declared known bot is following your robots.txt exclusions. Bots that only visit 1 path are likely to see they are added to your robots.txt exclusions, and cease requests to your site, where bots that have continued to visit many distinct paths on your site are likely ignoring the robots.txt file and may warrant investigating further.
This feature has been automatically enabled where are robots.txt is easily visible to our systems, so is not automatically available for all customers. If you would like to work with us to have this information available for your accounts please get in touch with your Customer Success Representative.
