Every machine on your floor runs software all day without asking anybody first. Most of it belongs there. Trouble starts with the part that does not, and a program nobody is watching gets the whole night to itself. Six lines at this counter, and all of them finish at a desk with a person sitting behind it.
Matching names went out with the rotary telephone. The SentinelOne agent judges a program by its conduct on the machine underneath. Which processes it started, what it opened, who it dialed, and whether all of that adds up to documents getting locked, hauled off, or a slow stroll from one desk to the next. The call still gets made with no link to anywhere, which is exactly what a laptop somewhere over Nebraska requires.
Fluency collects what the agents say and stands it next to everything else. Sign-in records, mail records, network records, and logs out of tools already sitting in your budget. A case therefore turns up at our desk carrying enough context to be settled rather than merely observed.
The first line watches, sorts and advises. The wide line reads several sources together, so a sign-in out of a state nobody visited and an odd program on a laptop stop being two unrelated shrugs. The containment line brings hands: the machine comes off the network and goes back to how it was while the engineer is still reading.
Cluster nodes get lines of their own. Nodes and laptops are different animals, the agent does not behave the same across both, and folding one into the other would quietly falsify your invoice. Count nodes. A pod is not a unit.
Every figure below is pulled live out of billing while the page opens, which means the number printed is the number a card would see. Whatever you add rests on the order pad, and it stays there afterwards.
A small program rides along on every covered machine and judges software by how it acts. Not by a list of bad names, which stopped being enough years ago, but by what a program does once it starts running. When something acts like theft, sabotage or a lock being changed on your own files, a Fortify 24x7 engineer picks up the case and tells you in plain words what needs doing.
| Runs on | SentinelOne, with Fluency joining the dots |
|---|---|
| Machines | Windows, macOS and Linux |
| When it fires | You get told, advised, and walked through the cleanup |
| Off the network | Judgment continues with nothing to phone home to |
| Who answers | Fortify 24x7 engineers, day and night |
| Meter reads | Protected endpoints, one at a time, each month |
The same watch, only it stops looking at one machine at a time. Sign-in records, mail records and network records get read next to what the agent saw, so a strange login in one state and an odd program in another stop being two small shrugs and become one case worth opening.
| Runs on | SentinelOne, with Fluency reading wider |
|---|---|
| Reads | Endpoints, sign-ins, mail and network |
| When it fires | You get told, advised, and walked through the cleanup |
| Kept for | A long enough stretch to work backwards through |
| Suits | Shops already living inside Microsoft 365 or Google Workspace |
| Meter reads | Protected endpoints, one at a time, each month |
The wide watch, with hands. Cross the line and the machine comes off the network and goes back to how it stood, while the engineer is still on page one of the case. Three o'clock on a Sunday morning is the hour this line pays for itself.
| Runs on | SentinelOne with automatic response switched on |
|---|---|
| Cutting off | The affected machine is isolated from the network |
| Putting back | Reverses what a convicted program changed, where the system allows it |
| Checked by | A human reads back every automatic action after the fact |
| Suits | Payroll desks, signing boxes, the machine that runs the shop |
| Meter reads | Protected endpoints, one at a time, each month |
Watch for containerized work, billed by the node so the number on your bill is a number your platform engineer already keeps in their head. Pods come and go all day. Nodes are what you actually pay for, so nodes are what we count.
| Runs on | SentinelOne for Kubernetes |
|---|---|
| Watches | How workloads on the node behave once they are running |
| When it fires | You get told, advised, and walked through the cleanup |
| Who answers | Fortify 24x7 engineers, day and night |
| Meter reads | Cluster nodes, one at a time, each month |
Node watch with the wide reading switched on, so what happens inside the cluster gets read beside who signed in and what the laptops were doing. A workload behaving oddly is a curiosity. A workload behaving oddly right after an account was used from somewhere new is a case.
| Runs on | SentinelOne for Kubernetes, read wider by Fluency |
|---|---|
| Reads | Node activity, sign-ins, endpoints and network |
| When it fires | You get told, advised, and walked through the cleanup |
| Kept for | A long enough stretch to work backwards through |
| Meter reads | Cluster nodes, one at a time, each month |
The node line with the brakes wired in, for clusters running something you would hate to leave misbehaving until somebody opens the office. The action happens first and the write-up reaches you after, with the reasoning attached.
| Runs on | SentinelOne for Kubernetes with automatic response |
|---|---|
| Cutting off | Automatic action against the workload that misbehaved |
| Checked by | A human reads back every automatic action after the fact |
| Suits | Production clusters carrying somebody else's work |
| Meter reads | Cluster nodes, one at a time, each month |
Everything below is part of the monthly price. None of it is a separate quote later on.
Watching makes a solid control and a hopeless promise. Its boundary is printed below, out loud, so that working out what else the shop owes you takes about a minute.
Heads up: card statements show FORTIFY 24X7 - Stars and Stripes Tech is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.