RISK SCORING
A risk read your team can explain, not a black-box verdict
Noxtica turns browser, device, and network evidence into a score, a named risk level, a confidence value, and reasons. Your team maps them to its own actions.
WHAT YOU GET
Outputs your team can read together
Review the fields together. A higher score with limited confidence can call for more evidence rather than a hard block.
Noxtica
Risk level
- Minimal
- Low
- Medium
- High (example read)
- Critical
Confidence
LimitedHighIn this example: limited.
How much evidence supported the read. It is separate from the level.
Named reasons
- Automation and bots
- Fingerprint tampering
- Infrastructure abuse
Example reason families. Visible reasons follow your role and the evidence gathered.
Your policy
Noxtica supplies the read. Your policy supplies the action, set for each route. Start in observation mode.
- Allow
- Observe
- Step up
- Review
- Block
Score and risk level
A numeric score places each assessment on an ordered risk scale. A named risk level maps it to route-specific policy bands.
Confidence
Confidence is separate from severity. It shows how much evidence supported the assessment, so limited confidence can lead to observation or a reversible step-up.
Named reasons
Each assessment traces to named evidence categories instead of an unexplained label. Visibility follows workspace role and the evidence gathered for that event.
Console review and calibration
Review score distributions, reason breakdowns, and decision history in the console. Your operators tune thresholds. Noxtica does not claim automatic learning.
HOW IT WORKS
From evidence to an action you choose
Noxtica supplies the read. Your application, or a policy you provision separately, supplies the action.
Your page
Browser collector
Gathers browser, device and network context. Optional collection follows your consent and admission settings.
Noxtica
Risk read
Evidence from the page
A score, a risk level, a confidence value and named reasons.
Your server
Server lookup
Level, confidence, reasons
Your backend reads the assessment with a server-held credential. The page callback and the console expose it too.
Your policy
Choose the action
Risk bands
Allow, observe, step up, review or block, set in your own backend. Start in observation mode.
Gather evidence
The browser collector gathers browser consistency, automation, device, and network context. Optional collection follows your consent and admission settings.
Score and explain
Noxtica returns a score, a risk level, a confidence value, and named reasons. Your page callback, your server lookup, and the console expose the result.
Choose the action
Map risk bands to allow, observe, step up, review, or block in your own backend. Start in observation mode and compare proposed actions with known outcomes.
WHERE IT FITS
Decisions a risk read can inform
Use it where the cost of being wrong differs by journey.
Signup and login
Set thresholds per journey. A high-value account change can ask for step-up earlier than a page that just shows content.
Abuse queue triage
Use reasons to prioritize reviews, protect expensive routes, and allow expected automation without loosening policy for everyone.
Policy review
Compare what a policy did, or would have done, with confirmed outcomes before you change enforcement.
HOW TEAMS CONNECT
Browser callback, server lookup, and console
Scoring uses the same browser script and server lookup as Device Intelligence. Evaluation access is required.
- Browser script: the page callback exposes the score, risk level, confidence, reasons, device handle, and cache state.
- Authenticated server lookup: your backend reads the current risk assessment and device timestamps with a server-held credential.
- Operator console: review score distributions, reason categories, and calibration views. Navigation follows operator role and tenant scope.
LIMITS TO PLAN FOR
What a score cannot tell you
Plan for these boundaries before you set a threshold.
- Evaluation access. Core scoring belongs to an activated web integration. Advanced calibration, metered scoring, and network reputation context depend on plan, role, and tenant configuration.
- Enforcement is controlled. Challenge, limit, and block actions need controlled provisioning and explicit configuration for your tenant. Detection alone does not trigger them.
- Estimates, not facts. A score does not prove a visitor is human, fraudulent, or safe. Output is probabilistic, and no accuracy or false-positive rate is promised. Your team makes the decision. Read the disclaimer.
- Missing evidence is not low risk. Blocked scripts, privacy browsers, corporate networks, and assistive technology can hide evidence or resemble abuse. Treat unknown as unknown.
Scores, reasons and verdicts are probabilistic estimates, not statements of fact. Your team makes every decision.Read the disclaimer
FAQ
Common questions
Does Risk Scoring decide for me?
No. It returns evidence and a risk read. Your team chooses the action. Challenge, limit, and block actions need controlled provisioning and explicit configuration for your tenant.
Can I see why an assessment scored the way it did?
Assessments carry named reasons, visible according to your role and the evidence gathered. Internal weights and detection mechanics are not published.
Does the score learn on its own?
No. Operators tune thresholds and policies today. Noxtica does not claim automatic learning from your outcomes.
Related products
RISK SCORING
Evaluate the read against your own traffic
Request a technical evaluation. Start in observation mode. Compare proposed actions with your confirmed outcomes, and change enforcement after you review the results.