Risk score mapping for nevisAdapt
For a proper functioning of the nevisAdapt service, the risk scores are mapped in the riskscore-mapping.properties file. The complete file path is /var/opt/nevisadapt/conf/riskscore-mapping.properties.
The scores in the file have been defined by the nevisAdapt team. It is recommended that you do not modify them. To adjust the service to your needs, you can use the analyzer weights in the NevisAdaptAuthState or the preconfigured profiles in nevisAdmin4.
The section below lists all properties that you can set in the riskscore-mapping.properties file. These properties correspond with the results of the observations made by the modules in regard to a user's HTTP request. Such observations are, for example, whether the user device is known, private or shared, or whether the request comes from a suspicious or trusted country. By mapping a risk score to a property/result, you express the severity of the security risk represented by this result: The higher the risk score, the higher the risk.
The risk score calculation for a user request is based on the risk score mapping defined in the riskscore-mapping.properties file. Each user request results in three different risk scores: one for the Device Recognition module, one for the Fingerprint module, and one for the Geolocation module. The module's overall risk score is the sum of the risk scores of the module's analyzers. The maximum possible risk score for a module is "1.0" (as defined in nevisDetect).
For a sample calculation of a risk score, see the chapter Example - Calculating the risk score for the Fingerprint module.