Machines drift. Patches stall, a laptop leaves with a contractor, somebody turns off the thing that was slowing them down, and a handset three sites away quietly stops updating. This bay keeps the fleet in a known state and tells you when a machine has left it, which is the whole of the argument.
N-able N-sight reports health and inventory, approves and deploys patches on a schedule that fits your shift pattern, runs scripts, and lets an engineer reach a machine without asking somebody on the floor to read numbers off a screen into a phone.
Web and name filtering comes off that same agent, so the control travels with a laptop to a customer site, to a hotel, and to a kitchen table. Nothing gets racked, and nothing stops working the moment a device leaves the building.
Addigy manages the Mac and iPad estate properly: zero-touch enrollment, configuration profiles, encryption state, software delivery, and an update policy that does not ambush anybody mid shift.
Zimperium sits on the handset itself. Your supervisors approve purchase orders and read drawings on phones, which makes those phones endpoints whether anyone has written that down or not. Detection sits on the handset itself instead of in a console waiting on a round trip.
Every rate on this page comes live off the billing service. Anything locked on stays on the worklist while you read on.
The line that keeps the fleet in a known state. Health, inventory, and patch level are visible in one place, and an engineer can reach a machine without asking somebody on the floor to read numbers off a screen.
| Mounted on | N-able N-sight agent on each managed device |
|---|---|
| Isolates | A machine drifting out of its patch and configuration baseline |
| Retained for | Inventory and patch state, kept while the subscription is live |
| Released by | A Fortify 24x7 engineer, or your own approver in the console |
| Signed off by | The engineer who ran the change, in the device history |
Name resolution and web traffic filtered on the device itself, so the control travels with a laptop to a customer site and to a hotel rather than staying behind at the office firewall.
| Mounted on | N-able N-sight web protection, riding the fleet agent |
|---|---|
| Isolates | A request to a destination your policy does not permit |
| Retained for | Request and bandwidth reporting, to your own policy |
| Released by | A Fortify 24x7 engineer adding the exception you ask for |
| Signed off by | Whoever holds the named approver role on your account |
Apple hardware managed properly rather than trusted to behave. Enrolment, configuration, software, and update state are handled from one place, including the machines that never come back to a desk.
| Mounted on | Addigy, enrolled on each Mac, iPad, or Apple TV you cover |
|---|---|
| Isolates | An Apple device sitting outside the configuration you set for it |
| Retained for | Device and profile records, kept while the subscription is live |
| Released by | A Fortify 24x7 engineer, or your own approver in the console |
| Signed off by | The engineer who applied the profile, in the device history |
The phones your supervisors read mail and approvals on are endpoints, and almost nobody treats them as such. This puts detection on the handset rather than trusting the app store to have caught everything.
| Mounted on | Zimperium, installed on the iOS or Android handset |
|---|---|
| Isolates | A hostile network, a hostile application, or a tampered handset |
| Retained for | Handset findings, retained the whole time a line is running |
| Released by | A Fortify 24x7 analyst, once the handset finding is worked |
| Signed off by | The handset holder, and the engineer who cleared the finding |
Fleet management is about knowing and holding a state. Here is what fleet management will not do.
Heads up: card statements show FORTIFY 24X7 - Industry Lock Networks is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.