Custom Risk Score Provider Integration

It is possible to define a custom set of risk scores using the Proxy Risk Plugin pattern connection to any service with a REST endpoint. Make sure you add the Proxy Risk Plugin pattern to the list of risk plugins in the nevisdetect Core Instance pattern. It needs a service URL for the risk score provider and a list of Risk Scores in the following format: equation mark, hashmark, and the hexadecimal RGB code for the color to use in the nevisDetect Admin GUI, for example:

RiskScoreName=#90ABCD

Service mapping must be defined between the RESTful address and the service to be invoked. Each mapping is on a different line. The supported methods are: getVersion, requestData, authenticationData, terminateSession, for example:

requestData=/processRequestData
terminateSession=/processSessionTermination
getVersion=/getVersion

More details regarding the Proxy Plugin can be found in Plug-in Proxy.