Website name as configured in Web Security Manager.

The total number of requests processed during the learning process.

Total number of unique URL paths identified.

Total number of unique parameter names identified. Uniqueness is determined by URL path. Two parameters with the same name but mapped as belonging to different URL paths are therefore identified as two unique parameters. When the policy is built Web Security Manager identifies parameters with similar names and input data as as global in scope and builds global patterns matching such parameters.

An indicator bar showing the progress of the sampling process.

Sampling is the process of collecting information about the website in terms of what paths/applications are used, what parameters do they take as input, what extensions are used for static content, etc.

An indicator bar showing the progress of the verification process.

The verification process 1) validates the data samples using statistical methods like analyzing spread in IP sources and time, number of requests, etc. and 2) verifies that the resulting policy covers the requests sampled.

As the Web Security Manager Learner extracts characteristics like extensions, specific directories in paths and global parameters (parameter names a number of applications take as input - like print=1) and even patterns used in global parameters the verification process may start before the Data sampling progress has reached 100%.

Verification is calculated as the number of sample runs in a row with no policy changes relative to the required number configured in learner settings.

When Verification has reached 100% Web Security Manager will either build and commit a new policy or notify the administrator by email that verification has reached 100% and a new policy can be built and committed.