Nobody should be buying a screen to stare at. What gets bought here is three things working as one: an agent close enough to the machine to read what a program is actually up to, a layer filing that finding beside every other finding in the shop, and a person on shift who makes the call at four in the morning. Each line locked into this forme carries the lot.
A register of previously bad files ran out of usefulness some years ago. SentinelOne watches conduct instead. Which process started which. What got opened, and what got written. Where a connection was aimed. Whether the overall shape of it reads like encryption, like harvesting, or like a stranger having a wander. None of that wants a live connection, so the laptop stuck in a departure lounge and the old machine at the back of the stockroom both keep their own counsel.
Fluency files each of those findings beside the others: sign in records, mail movement, network traffic, logs out of tools already on your bill. A finding reaching our desk therefore reaches it surrounded. Surrounded is what separates a notification from a fix.
The first sorts and advises. The second takes several sources at one time, so a sign in from an odd country, alongside a process behaving oddly on a counter machine elsewhere, stop turning up as two unconnected curiosities. The third isolates and reverses on its own authority, which is the property earning its keep at two on a Sunday.
Nodes carry prices of their own, and on purpose. A node is a different animal from a laptop. The agent behaves unlike itself on one. Rolling nodes quietly into a machine count would have your invoice telling a small lie. Count the nodes. Leave the pods alone.
Figures underneath come straight from billing when this page opens. Whatever you set falls into the composing stick and sits there until you are done reading.
The agent reads conduct where the conduct happens, so a laptop with no route home still makes up its own mind. Cross the line and a Fortify 24x7 engineer takes it from there. What you receive is one sentence saying what to do, not a graph to puzzle over.
| Set on | SentinelOne, with Fluency filing the sources |
|---|---|
| Prints | A case with a plain recommendation attached to it |
| Standing type | An agent that carries on judging with no network |
| Locked by | The Fortify 24x7 shift, whatever the clock says |
| Proofed by | A case trail you can read back yourself |
Detection widened. A sign in out of somewhere improbable, and a peculiar process on the till machine, arrive inside one picture instead of two, which is the only arrangement under which anybody ever joins them up.
| Set on | SentinelOne, filed together by Fluency |
|---|---|
| Prints | One case assembled out of several sources |
| Standing type | A longer keep across every source that is connected |
| Locked by | The Fortify 24x7 shift, whatever the clock says |
| Proofed by | A look back once the whole record has arrived |
The widened line with hands attached. Once the threshold is crossed, the machine is isolated and rolled back while an engineer still reads the case. That counts for most during the hours when nobody is anywhere near the counter.
| Set on | SentinelOne with response turned on |
|---|---|
| Prints | Containment, followed by a written account of it |
| Standing type | A response threshold agreed once and then left in place |
| Locked by | The Fortify 24x7 shift, whatever the clock says |
| Proofed by | A human read of every automatic move, after the event |
Detection for containers, priced per node, so the invoice agrees with what your platform engineer already counts. Pods churn all day long. Nodes are the thing being paid for.
| Set on | SentinelOne for Kubernetes |
|---|---|
| Prints | Run time findings out of the workloads on that node |
| Standing type | A node agent that outlives the churn beneath it |
| Locked by | The Fortify 24x7 shift, whatever the clock says |
| Proofed by | A case trail you can read back yourself |
Node detection carrying the filing as well, so cluster activity sits beside the account which reached it and the laptop that account signed in from. One account of events rather than three.
| Set on | SentinelOne for Kubernetes, filed together by Fluency |
|---|---|
| Prints | One case running across cluster, account and machine |
| Standing type | A longer keep across every source that is connected |
| Locked by | The Fortify 24x7 shift, whatever the clock says |
| Proofed by | A look back once the whole record has arrived |
A node line carrying response as well, for a cluster running something you cannot leave misbehaving until somebody unlocks the shop.
| Set on | SentinelOne for Kubernetes with response turned on |
|---|---|
| Prints | Containment, followed by a written account of it |
| Standing type | A response threshold agreed once and then left in place |
| Locked by | The Fortify 24x7 shift, whatever the clock says |
| Proofed by | A human read of every automatic move, after the event |
Detection is a fine control and a poor guarantee. Marked up here is what the six lines cannot cover, which is how you work out what else the shop needs.
Heads up: card statements show FORTIFY 24X7 - SecureBiz IT is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.