Site-bound identity
Each licensed website registers independently with a revocable connection token.
Shared intelligence, local decisions
A wider view of risk—without handing control to the cloud.
Nexus Threat Network exchanges compact high-confidence security signals through site-bound credentials, while every protected website keeps the final enforcement decision local.
Site-bound tokensAsynchronous outboxConsensus safeguardsExpiring records
NEXUS THREAT NETWORKCONNECTED
Site identityLicensed token validated
Signal acceptedIndependent source context retained
Record expiresLive feed remains time-bound
Consensus safeguards
Self-origin, protected infrastructure and same-host clustering rules reduce easy network poisoning.
Local enforcement
Network records influence scoring; they do not automatically take control of the site.
Privacy-conscious intelligence
Share attack evidence, not customer activity.
The network is designed around security context such as source, event class, risk and time—not passwords, form contents, orders or page content.
- High-confidence signal categories only
- Token-secured registration and feed access
- Accepted, ignored and rejected delivery accounting
- Expiration-aware active records and local last-good cache
Capability map
A network layer built around bounded trust.
The architecture separates collection, validation, distribution and local response.
Licensed site registration
An active licence can register the website and receive a site-bound token plus managed service endpoints.
- One website per identity
- Revocable token
- No public endpoint fields required
Asynchronous signal outbox
High-confidence events are queued locally and sent later without delaying the visitor request.
- Bounded retries
- Backoff behavior
- No synchronous request dependency
Source-independence checks
Self-origin suppression, infrastructure protection and same-host grouping reduce false consensus.
- Server-IP safeguards
- Independent-source weighting
- Accepted/ignored/rejected state
Local scoring and confirmed blocking
Feed records add risk context. Automatic blocking remains conservative and optional for confirmed records.
- Watch and score states
- Confirmed-only option
- Local final verdict
Operational flow
Four stages behind the shared intelligence layer.
The network helps sites learn from one another without becoming a single remote kill switch.
Register
A valid Nexus PRO licence creates the independent site identity.
Queue
A qualifying local event enters the bounded signal outbox.
Validate
The service checks token, origin, source independence and protected infrastructure rules.
Receive
Fresh network records are cached locally and used as extra scoring context.
Strengthen local evidence with fresh network context.
- Keep every site separately identified
- Expire active records
- Suppress self-origin reporting
- Preserve last-good feed data during temporary failures
Create blind cloud enforcement.
- Share passwords or checkout data
- Count one hosting cluster as many independent witnesses
- Block from weak network context alone
- Break older clients when feed formats evolve
Feature questions
What buyers usually want to know.
What data is shared?
Compact security-signal context such as source IP, event category, risk and timing. Passwords, cookies, form contents, orders and page content are not part of the intended signal payload.
Can the network remotely block visitors on my site?
No. The local Nexus installation makes the final decision. Network records are risk context, with optional confirmed-record blocking controlled locally.
What happens if the service is temporarily unavailable?
The site continues using its local protection and last-good cached intelligence. Signal delivery retries in the background.
Does every Agency site share one network token?
No. Each website uses its own licence key and site-bound network identity.
Lumiverse Nexus PRO
Security intelligence that respects where the evidence came from.
Nexus Threat Network access is included while the Nexus PRO licence is active.