Pulse · Monitoring + Managed SOC
Continuous monitoring, with a SOC that answers the alert.
SIEM and EDR editions delivered as a monitored service: alerts reach someone accountable, and the response is written down.
Detection, compliance mapping and Fortress telemetry from one sensor fabric.
Threat feed — severity KPIs, alert ranking and the command sidebar
Award-winning Risknox platform
Platform tour · 4 modules
See Pulse in operation.
From the queue an analyst opens at shift start to the framework evidence an auditor asks for afterwards.
Module 01 · Command Center
Every threat in one queue
Severity-tiered KPIs sit above a ranked alert list, so the shift starts with the incidents that matter rather than a raw firehose.
Severity KPIs
Critical and high counts beside the total, with changes since the last shift.
Severity bars and threat ranking
Alerts by severity next to the top threat types affecting your estate.
Command sidebar
Posture, investigate, assets, vulnerabilities, compliance and endpoints in one rail.
Threat feed — severity KPIs, alert ranking and the command sidebar
Module 02 · Inventory
Know every box you own
Agents report online state, operating system, address and health, so the estate is a register rather than a guess.
Agent KPI trio
Registered agents split into online and offline, so gaps needing attention are explicit.
Searchable inventory
Agent name, identifier, IP address, OS and status per machine, with detail on click.
Health and connection trend
Status distribution, fleet health score and connection trend beside the table.
Asset and agent management — inventory rows, status distribution, fleet health
Module 03 · Protection
Endpoints that defend themselves
Quick scans and full system scans run from the same console, with detection rates and coverage shown against the fleet.
Quick and full scans
Trigger targeted or fleet-wide sweeps without leaving the dashboard.
Scan metrics
Scans run, files and data processed, and clean-versus-detected rates.
Coverage and threat database
Endpoint protection coverage per asset, backed by a maintained threat database.
Endpoint protection — scan activity, detection rate and coverage status
Module 04 · Compliance
Threats mapped to every control
Every detected threat is mapped to the controls it touches, so monitoring output becomes framework evidence rather than a separate exercise.
Threat-to-control mapping
Each alert tied to the controls it affects, with mapping gaps visible.
Top violated controls
Violation counts per standard, led by the controls your estate keeps hitting.
Framework status
Coverage across CIS, SOC 2, ISO 27001, GDPR, HIPAA, NIST-CSF and PCI-DSS.
Compliance mapping — violated controls chart and framework breakdown
What it does
The capabilities that matter.
Detection without triage is noise, and noise is what attackers rely on.
SIEM edition
Log ingestion, correlation and alerting across your estate, tuned to your environment rather than shipped defaults.
EDR edition
Endpoint detection and response with investigation and containment actions on affected hosts.
Managed SOC
Our analysts work the queue around the clock: triage, escalation, containment guidance and a written record.
Containment playbooks
Pre-agreed actions for the incidents that matter most, so a decision does not wait for a meeting.
Monthly posture review
What was detected, what it means, and which control gap keeps producing it.
Feeds Fortress
Detections and control health from Pulse flow into Fortress, so the risk figure moves when your monitoring finds something, not at the next annual review.
Monitoring engine
Sense the estate. Work it down.
Posture summaries, threat correlation, compliance mapping and quantification feeds computed from the same telemetry.
Posture
Posture and exposure summary
A living summary of what you own, what is exposed and what changed since the last review — the first screen every shift opens.
- Total, critical and high alert rollups
- Affected-asset and attack-source context
- Change tracking across the shift
- Pre-prioritised investigate queue
Threat intel
Threat correlation
Global threat intelligence correlated against your estate, so prevalence is read against the assets you actually run.
- Threat-type prevalence rankings
- Brute force, malware and exfiltration tracking
- Source and origin context per alert
- Correlated feeds rather than static lists
Compliance
Compliance mapping engine
Detected threats mapped to controls across seven frameworks, with violated-control analytics showing where to harden next.
- Threat-to-control mappings per alert
- CIS, SOC 2, ISO 27001, GDPR, HIPAA, NIST-CSF, PCI-DSS
- Top-violated-control analytics
- Framework status breakdown
Fortress handoff
Quantification-ready telemetry
Pulse signals stream into Fortress for dollar-quantified loss modelling, so monitoring telemetry becomes board numbers without re-entry.
- Asset and alert telemetry export
- Severity-weighted risk inputs
- Fortress loss-model compatibility
- Compass underwriting lineage
Defense suite
From sensor to response.
Detection, assets, blocking, endpoint protection, vulnerabilities and forensics as one continuous loop.
Threat feed and detection
Severity-tiered alert feed with top-type rankings and a triage queue that stays quiet until it matters.
Asset and agent management
Per-machine inventory with IP, OS and status, plus fleet health and connection trends.
App and web blocking
Policy enforcement on applications and web destinations, driven by threat intelligence.
Endpoint protection
Quick and full-system scans with live metrics, detection rates and coverage proof across the fleet.
Vulnerability management
Severity-tiered vulnerability tracking with asset context and named remediation owners.
Log retention and forensics
Long-retention telemetry with investigate-grade search for breach forensics and audits.
How it works
Monitored in three moves.
Connect the estate, let the queue be prioritised for you, then work the response and the evidence.
Ingest and discover
Connect cloud accounts, DNS zones and network endpoints, and install agents on the estate.
Correlate and prioritise
Detection is cross-referenced against global threat intelligence and ranked by severity.
Contain and review
Alerts are triaged with recommended action, then reviewed in the monthly posture report.
Who it’s for
One queue, four different jobs.
Coverage without headcount
CISOs and security directors
Full attack-surface visibility without staffing a round-the-clock SOC.
Kill alert fatigue
SecOps and SOC analysts
Prioritised signals with playbooks attached, instead of raw noise.
Ship and stay covered
Cloud and DevOps teams
Agents and posture checks inside every workload you deploy.
Intel that acts
Threat intelligence teams
Global feeds correlated against your telemetry and ranked by prevalence.
One pipeline
Govern → Monitor → Quantify → Underwrite.
Pulse signals feed Fortress models, and Fortress figures flow into Compass terms. No re-entry, no evidence loss.
FAQ
Answers SOCs ask for.
What does Pulse monitor?
Internet-facing domains, cloud workloads, APIs, endpoints through lightweight agents, and unmanaged shadow-IT assets. New findings are surfaced against the rest of the estate.
How does prioritisation reduce alert fatigue?
Behavioural anomaly detection is correlated against global threat intelligence and ranked by severity tier, so analysts open a triaged queue instead of a raw firehose.
How do app and web blocking and endpoint protection enforcement work?
Policies push to endpoints: risky applications and destinations are blocked by intelligence-driven rules, while quick and full-system scans run on demand with coverage tracked per asset.
How does Pulse feed Fortress and Compass?
Asset, alert and posture telemetry streams into Fortress for dollar-quantified loss modelling, which in turn gives Compass underwriting the same lineage.
How is Pulse deployed?
Agents install on endpoints and cloud connectors onboard without disruption, so the first prioritised signals arrive from the estate you already run.
Get started
Monitoring is cheaper when the risk is already quantified.
Pulse prioritises what Fortress says costs the most, so the queue reflects commercial impact rather than severity labels.