Search Results

The compliance monitor (codename Krahken) is intended to collect all data from our other products and present them in a unified portal. Additionally it has 2 main purposes:  Adding functionality for Compliance Scans and Analytics Adding functionality for A...

General Information In the world of website compliance, a lot of differnt compliance violotions can occour. Therefore we decided to make a clear separation of those violations and introduced different violation categories: Regulatory Violations Business V...

There are 2 types of actions, that can bei set to resolve issues: Resolve / Acknowledge Ignore Resolve an issue   By resolving an issue, the compliance monitor assumes that the cause has been fixed.  e.g.: If you resolve an issue for a cookie named...

When working with the compliance monitor, you will likely very often see the term "regulatory" or "business" in combination with "compliance".  There is a simple reason for that: Compliance is more complicated than security monitoring.  While security foll...

    This how-to describes how it is best to reproduce cookie violations, as this is often a very confusing topic. First of all it would be good to know, how exactly our crawler works in this case:  How Nimbusec visits websites The crawler of Nimbusec is te...

Issues can be auto acknowledged to simplify the issue handling process by keeping most of the transparency.  What does it do? If there is a rule, that allows e.g. a specific cookie to be set on a website, the issue will be auto acknowledged on our side. Th...

Suspicious Redirects What is it? A suspicious redirect is a redirect that has changed. Redirects are tracked with each scan, and if the redirect chain changes e.g. to a malicious website, or doesn't match the expected pattern a warning for suspicious behavio...