Set it once. Secuno keeps it that way.
A setting that was right last month is not a control. Secuno applies your configuration, checks it every fifteen minutes and puts it back when something changed it, for every client from one section, beside Intune rather than against it.
- 52 SETTINGS IN THE CATALOGUE
- CHECKED EVERY 15 MINUTES
- WINDOWS AND LINUX
- 02:47 · changed on the device
- 03:00 · put back at the next check
Routine work such as signature updates never counts as drift.
Settings that stay set.
A profile is a set of settings from a fixed catalogue. The agent applies them and you see per device whether each one holds, and which profile it came from.
Profiles and the full catalogue- Firewall
- Defender protection
- 19 ASR rules
- BitLocker + escrow
- Managed local admin
- Local Administrators
- Screen lock
- USB storage
- SMB signing, SMBv1
- LLMNR, NetBIOS, WDigest
- LSA protection
- Remote Desktop, NLA
- UAC, AutoRun
- Audit policy
- Script block logging
- Password + lockout
- Registry values
- USB storage
- SSH root + passwords
- SSH hardening
- Kernel + network sysctl
- Blocked modules
- Disabled services
- Password policy
- Core dumps
- auditd
- Secure Boot
- Tamper Protection
- Linux host firewall
Start from a baseline
Settings catalogue, an endpoint security template or a security baseline for Windows workstations, Windows servers or Linux servers.
See the impact first
Before you save, a preview shows per setting on how many devices the profile would win, lose to another profile or be blocked by Group Policy or an MDM.
Leaves no trace when it goes
Take a setting out of a profile and the agent puts back the value from before Secuno changed it. BitLocker is never switched off automatically.
Secuno never fights another tool.
Most clients already have a GPO, an MDM or a previous admin's script. A tool that overwrites them every fifteen minutes causes more incidents than it prevents, so Secuno steps back and says so.
Secuno reads each connected tenant's Intune policies every six hours and shows them beside its own settings. It never changes them.
- Succeeded
Applied and holding at the last check.
- Pending
Waits for a restart or the device's maintenance window.
- Managed elsewhere
A Group Policy or MDM policy owns it. Secuno does not write it.
- Conflict
Something changed it back three times in a day. Left alone until the profile changes.
A bad setting meets ten devices, not ten thousand.
Every change to a profile is a new version that moves through stages, each held for a soak time. Software assignments and monitors roll out the same way.
How the gate decidesPilot
Devices tagged pilot
Your own canaries, chosen by tag
10%
A tenth of the remaining devices
Held for the soak time before moving on
50%
Half of the remaining devices
Stage sizes are configurable
100%
Every targeted device
Only after every earlier stage held
Stops the rollout at once when more than 5% of reporting devices fail a changed setting or go silent.
Pause, resume, advance or publish now when you are sure. Abort sends the published values again as a new version.
Profiles enforce. Policies judge.
A compliance policy says what a device must meet and what follows when it does not. It changes nothing on the device.
- COMPLIANT
Every rule passes.
- IN GRACE
A rule fails. The clock you set is running.
- NONCOMPLIANT
Grace is over. The actions you scheduled follow.
Rules on what you already measure
Any device compliance check, such as BitLocker, Secure Boot, TPM, firewall, antivirus and signatures, UAC, patches current or an operating system still in support. A catalogue setting holding a given value, checked without enforcing it. A minimum or maximum OS version. The agent checked in within a number of days.
Grace first, consequences after
A device is compliant when every rule passes, in grace when one fails, then noncompliant. You schedule what follows in days from the first failure: mark it noncompliant, notify the client's admins with the devices named, raise a risk per device that resolves when it passes again. A rule with no data reads not evaluated, never compliant.
Block noncompliant devices in Entra
Per Microsoft 365 connection, and off until you switch it on, Secuno writes each Windows device's verdict to an Entra device attribute every 15 minutes. A Conditional Access policy can filter on it. Devices synced from on-premises Active Directory cannot be written, and switching it off clears what Secuno wrote.
Monitors, software and keys, from the same section.
Monitors that fix what they find.
A breach opens one alert and can run an approved script. If the script fixed it, the alert is marked self-healed and never becomes a ticket.
How monitors healSOFTWAREThe right software, kept that way.
Mark an app required and it stays installed. Installs run through the same queue as patches, inside the maintenance window.
Required, one-time, availableKEYSThe recovery key is there when the laptop is not.
BitLocker keys and local admin passwords are escrowed encrypted. Every reveal asks for a reason, is audited and leads to a rotation.
How escrow works- Low disk
- Service or systemd unit
- CPU
- Memory
- Windows event ID
- Script check
- Certificate expiry
- TCP port
- Ping
- Linux journal
- Device offline
- Backup too old
Powerful actions, with a second pair of eyes.
Being able to manage a device means being able to break it. The risky actions need a second person, and none of them happens without an audit record.
Lock and retire
Lock locks every session on the device, with an optional message first. Retire puts back every setting Secuno changed and then decommissions the device. Escrowed keys stay until the client is offboarded.
A wipe takes two people
Wipe works on Windows workstations only. You type the hostname, and a second person with access to that client approves within 24 hours. Automation rules and the command API cannot send a lock or a wipe.
No audit record, no action
Wipes, locks, key and password reveals, rotations and approvals are written to the audit log in the same transaction as the action. When the log cannot be written, the action is refused.
What MSPs ask first.
Does this replace Intune or Group Policy?
It does not have to. Where a GPO or MDM policy already owns a setting, Secuno reports it as managed elsewhere and does not write it. Secuno also reads your Intune policies and shows them beside its own settings, and it never changes them. Use Secuno profiles for clients without Intune and for the hardening settings your MDM does not cover, and see compliance for all of them in one place.
Every setting where you left it.
One agent, one console, one place where a finding turns into the setting that fixes it. We will show it on a fleet like yours.