Skip to content

PULSAR

SECURITY

TR

Stop 00 · Signal

PSR B1919+21, 1967

The paper chart of a radio telescope in Cambridge showed a pulse repeating every 1.337 seconds. The period was so stable that the recording was briefly nicknamed "LGM-1". The source was not a civilisation but a neutron star, the remnant of a star that collapsed under its own gravity: about 20 km across, more massive than the Sun.

Rotation periods range from milliseconds to seconds; the beams leaving the magnetic poles sweep the observer once per turn and register as a pulse. The most stable pulsars rival atomic clocks. That is where the system takes its name: a continuous, periodic signal you can verify on every turn.

Stop 01 · Route

Detection and response, resident on the server

Pulsar is a detection and response (EDR) layer that runs continuously on the server. Telemetry collection, behavioural anomaly detection, integrity verification and application-layer filtering are parts of one watch. It is not publicly available.

The route follows an attack through the MITRE ATT&CK tactics in order: reconnaissance (TA0043), initial access (TA0001), persistence (TA0003), impact (TA0040) and exfiltration (TA0010). Each stop describes what is observed at that stage and what outcome is produced.

Stop 02 · Pulse

A baseline per machine

CPU, memory, disk, processes and service response times are measured continuously, building a behavioural baseline for each machine. Deviations are evaluated against that baseline. Loss of the telemetry stream is an event in itself.

Live trace receiving telemetry

System telemetry is collected continuously; loss of the stream is treated as an event.

Telemetry
continuous
Baseline
per machine
Stream loss
event
Alerting
correlated

Stop 03 · TA0043

Reconnaissance and enumeration

Attacks usually begin with active scanning. Traffic is modelled per source as a pattern, not as isolated events; requests that look harmless on their own reveal intent in combination.

  1. EnumerationSystematic probing of admin interfaces, backup and configuration file paths.
  2. Automated scanningRequest patterns specific to vulnerability scanners and fuzzing tools.
  3. Credential attacksBrute force, password spraying and credential stuffing, from a single or distributed source.
  4. ResponseThe source is progressively isolated at the network layer according to its behaviour.

Stop 04 · TA0001

Web application firewall

Every HTTP request passes through a WAF before it reaches the application. SQL injection (' OR 1=1), XSS (<script>), path traversal (../../), command injection and protocol violations are inspected against the OWASP Top 10 classes.

  1. Per-site tuningFalse positives are resolved with per-site exceptions; inspection strictness is tiered.
  2. Verified rolloutRule changes are validated before going live; a failed change is rolled back automatically and traffic is not interrupted.
  3. Audit trailEvery blocked request and every request flagged as suspicious is recorded individually.

Stop 05 · Before the patch

Virtual patching and vulnerability management

When a vulnerability is disclosed, an official fix often does not exist yet. In that window the exploit vector is filtered as a virtual patch; once the permanent fix is installed, the temporary rule retires itself. Log4Shell (CVE-2021-44228) in 2021 was exactly such a window.

System packages and application dependencies are matched against current CVE records every day. An alert is raised only when an affected version is actually present.

Stop 06 · Inside

Web shells and file integrity

A payload that slips past the filter leaves traces on the file system: executable content in an upload directory, a web shell planted in the application tree, a system binary that changed unexpectedly. File integrity (FIM) is verified continuously; every unauthorised change produces an event.

Authentication and authorisation configuration, network services and scheduled jobs are in the same scope. Every difference is reported as configuration drift.

Stop 07 · TA0003

Persistence mechanisms

After initial access, the attacker's priority is persistence: keeping access across a reboot. The machine's verified state is continuously compared with its current state; every difference is examined.

  1. Account manipulationNewly created or newly privileged accounts (T1136, T1098).
  2. Listening servicePorts that start listening unexpectedly.
  3. Tasks and servicesUnregistered scheduled tasks and services that start at boot (T1053, T1543).
  4. Anomalous sessionAdministrator sessions from an unusual source or time window.

Stop 08 · TA0040

Autonomous response to ransomware

In some scenarios delay means data loss. In those cases the system acts on its own and records every action with its reason.

Contain first, analyse later

The moment the encryption stage (T1486) is detected behaviourally, the responsible process is suspended and the spread is stopped.

The suspended process is not terminated; it is preserved as-is for forensic analysis. The way to decrypt the files is often inside that very process.

Stop 09 · TA0010

Exfiltration and DNS hijacking

Outbound traffic is a behavioural pattern too: volume, destination and timing are compared with the machine's baseline. Command-and-control (C2) traffic and unusual data egress are treated as suspicious until their cause is verified.

The domain's DNS records and registrar data are monitored. A record change that silently redirects traffic to other infrastructure (DNS hijacking) is detected.

Stop 10 · External surface

TLS and availability

Certificate validity, chain integrity and protocol configuration are checked regularly; a TLS endpoint that is about to expire or is weakly configured is reported long before any browser warning.

Service availability is measured both locally and from external vantage points; rising latency becomes visible before it turns into an outage.

Stop 11 · Exposed secrets

Secret scanning

Passwords, access keys and API tokens left in plain text in source code, environment files, configuration and shell history are searched for. The value itself is never transmitted; only its location is reported.

Stop 12 · Black box

Isolated backups and an immutable log

Isolated backups
Even if the server is fully compromised, backup copies cannot be deleted or altered; the copy ransomware goes after first stays out of reach. Restorability is tested regularly.
Immutable event log
Events are stored append-only; daily records are sealed and kept off the server. The answer to "what happened?" is never left in the attacker's hands.

Stop 13 · Upkeep

Self-healing, cookieless analytics

Unresponsive services are restarted and resource exhaustion is prevented; every automatic action is recorded. If a failure repeats, automation stops and the incident is handed to an operator.

Visitor analytics use no cookies or persistent identifiers: traffic volume, navigation paths and referrers are measured, individual users are not identified. An identity that is never stored cannot leak.

Stop 14 · Boundaries

What it never does, by design

Some things are not a setting; they were designed out from the start.

Content
Pages, images and customer records are never modified. Protection works on traffic and the system, not on content.
History
New records are appended, old ones are never edited. History cannot be rewritten afterwards.
Personal data
Passwords, email addresses and session tokens are masked before anything is recorded.

End of the route

From here on it is free flight: you can roam around the star.

Developed by