Microsoft 365 tenant
Admin approval required before users grant consent to third-party apps, old sign-in protocols retired, mail auto-forwarding to outside addresses stopped, Teams external and guest options reviewed.
Out of the box, most systems are configured for convenience. Ancient protocols remain enabled in case something still needs them, every user is allowed to hand a random app access to their mail, and the copier's admin page sits online guarded by “admin/admin”. Individually these are minor. Collectively they are exactly the foothold an intruder hopes to find. Think of a structural engineering practice in Ljubljana: an obsolete file-sharing dialect is still enabled on its server, anyone in the firm can let an unknown app read their Microsoft 365 inbox, and macros fire happily in attachments fetched from the web. Not one of these issues calls for a purchase. They are all switches. Hardening is the systematic job of reviewing those switches against respected references, mainly CIS guides and Microsoft baselines. Flipping a value is easy; doing so without upsetting anyone's work is the skill. Hence our routine: measure, pilot, roll out, and write down every deliberate exception along with the reason.
We tighten things a layer at a time, from the cloud tenant all the way down to the office printer, measuring before and testing after each change.
Admin approval required before users grant consent to third-party apps, old sign-in protocols retired, mail auto-forwarding to outside addresses stopped, Teams external and guest options reviewed.
Microsoft baselines delivered by Intune or Group Policy, internet-sourced macros blocked, PowerShell constrained, local admin accounts brought under control.
SMBv1 and NTLMv1 retired, needless services such as print spooling on domain controllers disabled, administrative tiers introduced, password rules modernised.
SSH by key alone, direct root access disabled, host-level filtering, unattended security updates and surplus packages stripped out.
Default logins replaced, unencrypted admin access removed, firmware brought current. Copiers, storage boxes and CCTV recorders are frequent weak points.
Automated checks run regularly to confirm hardened values are still in force, so a patch or a hurried tweak that undoes one does not go unnoticed.
Hardening done in a rush breaks things. Small, measurable increments avoid that.
Systems are scanned against the chosen baseline. You see each setting's present state, the target state and what changing it might affect.
Together we choose what changes and where an exemption is justified, for example an older line-of-business app that still relies on a legacy protocol.
Lab machines and early adopters go first, everyone else afterwards. Everything is applied by policy, so any step can be undone.
A fresh scan, plus the register of justified exceptions. Ongoing drift detection is available as a regular service.
The least expensive security upgrade is the one hiding in your existing settings. No extra product, dashboard or subscription is required, only care and consistency. A surprising number of breaches pivot on one default that ought to have been switched off long ago.
They come from the Center for Internet Security, a non-profit, and are drafted with input from practitioners worldwide to cover operating systems, cloud services and network devices. They cost nothing to download and are commonly cited as a practical, setting-by-setting reference, ISO 27001 projects included.
Not at all. Certain items will not fit your environment and some would upset older software. We keep the ones that are worthwhile and record a sentence or two on why the rest were skipped. Auditors view a reasoned exception far more kindly than an unexplained hole.
It stays switched on solely for the server and workstations that use that program and goes off across the rest of the network. The exception is logged as a risk, with a reminder to modernise or replace the software.
Undoing a policy-driven change takes minutes, and the pilot usually catches problems beforehand. Should one reach users anyway, contact helpme@apply.si; we reverse the change, diagnose it and put a precise fix in place.
Give us an idea of your systems and their numbers. We will recommend which layer is worth hardening first.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.