krupiq
Download

Blue Oil™

Why you.

What Blue Oil™ is

Blue Oil is the layer krupiq lays over your network. Like oil on water, it gives an intruder a surface that looks like the real thing and moves like it, while everything underneath stays untouched. Blue is the colour of the defender. The intruder spends their night on a network that exists only for them. You spend yours asleep.

The call comes at 3:40 in the morning. Screens you cannot read. Phones that will not stop. A number with too many zeros. Everyone asks what you did before. No one asks what the tools were called. Some spend that night negotiating. Others sleep through it, because the moment the first file was touched it was already over. By morning, there is nothing to explain.

  • 01

    Cat

    Sees without being seen. Silent, patient, already in position.

    Runs on your own machines and sends nothing of yours out. Real sessions are counted, never recorded.

  • 02

    Squid

    Clouds the water and changes shape in an instant. Gone before the predator reacts.

    The decoy shifts every five minutes, a little at a time, along a path drawn for your deployment alone. It never reacts to being probed, so probing teaches nothing.

  • 03

    Owl

    Turns its head 270 degrees. Sees everything. Hunts in total darkness.

    Every touch on the decoy is real. Nothing legitimate ever goes there, so there are no false alarms.

Safe for production

The decoy runs beside your production network, never in its path. Employees, applications and your own scanners notice nothing. Only the decoy changes.

State of affairs

The attacker is a machine. The defender is still a person.

What the numbers say, and what krupiq is built to change.

Industry figures on discovery, response, cost and fatigue, with sources, and what krupiq is built to change
SubjectThe figuresSince you opened this pageImpact
Zero-day and breach discovery
  • 312 days Zero-day exploit, active before detectionSymantec, Mandiant M-Trends
  • 183 days Breach identified, on averageIBM, Cost of a Data Breach
  • 6.9 years Lifespan of an undisclosed flawRAND
Fixed: time does not change itAttackers operate undetected for months while defenders stay blind to new exploits.
Time to action
  • 55 to 60 days Enterprise patch deployedPalo Alto Networks, Lansweeper
  • 64 days Breach contained, on averageIBM, Cost of a Data Breach
  • 5 days Disclosed flaw weaponisedGoogle
Fixed: time does not change itTesting and ticketing leave a two-month exposure window after a fix exists.
Global cyber damage and downtime
  • $10.5 trillion Total cyber damage a yearMcKinsey
  • $600 billion, $15,000 a minute Global 2000 downtime a yearSplunk
  • 7 to 24 days Average outageAcronis, Total Assure
$0in cyber damage worldwideDisruption costs up to fifty times the ransom, and most of the market is still unprotected.
Cyber and alert fatigue
  • 2,992, of which 42 to 63% ignored and 46 to 80% false Alerts a day, per SOCVectra AI, Microsoft and Omdia
  • 71 to 76% Analysts reporting burnoutUnderDefense
  • 95% Breaches involving human errorWorld Economic Forum
0alerts at one SOCOverwhelmed teams miss about fifty real attacks a year, and exhausted staff fall for MFA push-bombing.
What krupiq is built to do
  • 15 times faster Port scan foundmeasuredEmersa Labs, own tests (evidence from the signed record, on request)
  • 1 day, not 312 Zero-day exposuremeasuredEmersa Labs, own tests (evidence from the signed record, on request)
  • Lower: nothing real is reached Damage and downtimetarget
Measured in our own tests; the evidence is in the signed recordAn intruder spends their time on a decoy, so discovery is the first touch rather than the hundredth day.

The counters start at zero when the page opens and grow at the rates the sources give: $10.5 trillion a year in cyber damage, 2,992 alerts a day at one security operations centre. Nothing is random. A measured figure comes from Emersa Labs' own tests, with the evidence held in krupiq's signed record and shown on request; a target is what krupiq is built to do and has not yet been measured.

Sources: Symantec; IBM, Cost of a Data Breach; RAND; Mandiant M-Trends; Palo Alto Networks; Lansweeper; Google; McKinsey; Splunk; Acronis; Total Assure; Vectra AI; Microsoft and Omdia; UnderDefense; World Economic Forum; Emersa Labs, own tests (evidence from the signed record, on request).