System Administration for Business

Servers, identities and permissions (IAM) determine who can access which data and what happens when something fails. We manage the business’s systems layer on an ongoing basis, with updates, monitoring, documentation and change management.

Server racks with neat cabling

Servers, accounts
and permissions under watch

A system nobody looks at keeps working until the day it stops. Ongoing system administration means knowing that the updates were installed, the backup ran, the disk isn’t filling up and there’s no admin account someone forgot to close.

  • Security updates for servers and workstations on a schedule
  • Managing Active Directory, GPO and folder permissions
  • Monitoring and alerts before a fault stops work

Call +972-3-3801180

Who it’s for

  • Businesses with their own servers

    A file server, Active Directory, an accounting server or an application server, in the office or in the cloud, that need regular maintenance, updates and monitoring.

  • Organizations where permissions have sprawled (privilege creep)

    Employees who left and still have an account, folders everyone can see, and system admins who got their permissions for reasons nobody remembers.

  • An in-house IT person who needs professional backup (co-managed IT)

    Someone who handles day-to-day IT in the organization and needs a partner for projects, server updates, hardening and the days they aren’t available.

Sound familiar?

These findings come up in almost every first review of a business’s server environment.

  • Servers that haven’t received security updates in months
  • Accounts of employees who left are still active in the domain
  • Every employee is set up as a local admin on their own computer
  • The same local admin password on every computer in the organization
  • Folder permissions built up one at a time, and nobody knows who can see what
  • A fault is discovered only when an employee calls to say something isn’t working

What system administration includes

We manage the server and identity layer on an ongoing basis, and document every change.

  • Windows Server

    Installing, maintaining and upgrading Windows servers: file, print, application and RDS servers, including migration from versions that are out of support (end of support).

  • Active Directory and Entra ID

    Managing users, groups and computers, syncing on-premises AD with Entra ID (hybrid identity), and an OU structure that supports orderly policy.

  • GPO and policy

    Group policy for workstations and servers: security settings, drive and printer mapping and screen lock, managed from one place.

  • Permissions and privileged accounts (PAM)

    Folder permissions by group (RBAC), separation between a work account and an admin account, LAPS for local admin passwords and fewer domain admins.

  • Linux servers

    Managing Ubuntu, Debian and AlmaLinux servers: updates, hardening, web services and databases, secure access and monitoring.

  • Patch management

    System and security updates for servers and workstations on a schedule, with testing before broad installation and tracking of what wasn’t installed.

  • Monitoring and alerts

    Tracking availability, disks, services, backups and certificates, and alerting when something goes out of bounds, so it can be handled before work stops.

  • Documentation and change management

    Every change to a server or to permissions is documented: what changed, why and when. That way you can roll back and explain every setting.

What we take care of, in detail

Windows, identities and permissions

  • Windows Server: installation, version upgrades, roles and services, and migration from servers that are out of support
  • Active Directory: users, groups and OUs, domain controller health and replication between them
  • Entra ID: hybrid sync, MFA, conditional access and device registration
  • GPO: security baseline, workstation settings, resource mapping, password and lockout policy
  • DNS and DHCP: zones, records, scopes and reservations, and documentation of the addresses
  • File servers: folder structure, NTFS permissions and sharing by group, quotas and Shadow Copies
  • Windows LAPS: a unique local admin password for each computer, rotated and stored in AD or Entra ID
  • Privileged accounts: separate admin accounts, fewer Domain Admins, service accounts with least privilege

Linux, updates and monitoring

  • Linux servers (Ubuntu, Debian, AlmaLinux, Rocky): installation, hardening and service management
  • Secure server access: SSH keys, disabling direct root login and restricting access by source (IP allowlist)
  • Patch management for servers and workstations: schedule, test group, installation report and exceptions
  • Monitoring availability, resources and services (Zabbix, Uptime Kuma) with alerts by severity
  • Tracking the expiry of certificates and licenses, and versions reaching end of support (End of Life)
  • Collecting event logs from the servers (log management) and keeping them for investigation

Documentation and control

  • Documentation of servers, roles, service accounts and dependencies
  • Change management: what changed, when, by whom, and what the rollback plan is
  • Periodic access review and closing inactive accounts
  • Employee onboarding and offboarding procedures for AD, Entra ID and the systems
  • Periodic hardening checks for Active Directory (PingCastle, Purple Knight)

From the first conversation to an organized routine

  1. 1

    Environment review

    Mapping the servers, the domain, the accounts and the permissions, and checking the updates and backups.

  2. 2

    Findings report

    A list of gaps by severity (gap analysis): what is open to an attacker, what could cause an outage and what can be planned.

  3. 3

    Fixing and hardening

    Closing the urgent gaps in coordination, without stopping work and with documentation of every change.

  4. 4

    Ongoing management

    Updates, monitoring, periodic access review and keeping the documentation up to date.

Why system administration is also information security

An attacker who gets in through one computer looks for admin rights (privilege escalation) and a way to reach the servers. Much of what stops them is decided in day-to-day system administration, before any additional security product:

  1. A unique local admin password for each computer

    When every computer has the same admin account with the same password, one compromised computer is enough to move to all the rest (lateral movement). Windows LAPS generates a unique password for each computer that rotates automatically and is stored securely in AD or Entra ID, closing off that route.

  2. A work account and an admin account are two accounts

    A system admin who reads email and browses with an account that has domain rights exposes those rights to every malicious file that gets opened. Separating the everyday account from the admin account (PAM), and reducing the number of domain admins, greatly reduces the damage from a breach of one workstation.

  3. A security fix that wasn’t installed

    Once a vendor publishes a security fix, the details of the vulnerability are available to attackers too, and servers that weren’t updated get scanned and exploited. Orderly patch management includes a schedule, testing on a small group before broad installation, and tracking of servers that were left behind.

  4. Permissions by group and by role (RBAC)

    A permission given to an employee directly on a folder gets forgotten when they change roles or leave. When permissions are given to groups by role, it’s easy to check who sees what, close access when someone leaves and show that access to sensitive data is limited to those who need it (need to know). Since Amendment 13 to the Privacy Protection Law took effect, the Privacy Protection Authority has the power to impose administrative fines, including for breaches of data security obligations.

  5. Monitoring finds a fault before the user does

    A disk filling up, a service that went down, a failed backup or an expired certificate are faults you can see coming. Monitoring with alerts by severity makes it possible to handle them before they stop work, and retained event logs make it possible to understand what happened when a security incident is suspected.

Guide: New employee onboarding: an organized IT checklist

Frequently asked questions

About system and server administration.

Didn’t find an answer? +972-3-3801180

The work can be divided (co-managed IT). Your IT person continues with day-to-day user support, and we take on what requires depth or time: server updates, Active Directory hardening, projects and migrations, and cover during vacation or sick leave. Permissions and documentation stay shared and transparent to both sides.

LAPS is a Microsoft mechanism that manages the local admin password on every computer: each computer gets a unique password, it rotates regularly and it is stored in AD or Entra ID with access for authorized people only. Without such a mechanism, many organizations have one local admin password for all computers, and one compromised computer opens the way to all of them.

Yes, in a different form. Instead of an on-premises domain server, you manage Entra ID: users, groups, MFA, conditional access, device registration and policy through Intune. Even without servers in the office there are identities, permissions and devices that need to be managed and checked.

Sometimes, yes, which is why updates aren’t installed on everything at once. They go first to a small group (pilot group), we check that the critical systems work, and only then expand. A server that never gets updated is a bigger risk than the rare fault an update causes.

Yes. Ubuntu, Debian, AlmaLinux and Rocky servers, for example web servers, databases, application servers and internal tools. The management includes updates, hardening, secure access, monitoring and backup.

Because many of the decisions that determine whether an incident stays small are made in day-to-day administration: who is an admin, which updates were installed, which logs are kept and who can access the databases. The Privacy Protection Law and the Data Security Regulations require access control and documentation, and since Amendment 13 the Privacy Protection Authority is authorized to impose administrative fines. When this is neglected, the result is downtime, exposure of customer data and a review by the regulator.

Want to know the state of your business’s servers and permissions?

Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.

Business hours: Sunday to Thursday, 09:00 to 17:00

Existing client? Open a support ticket

Leave your details and we’ll get back to you

Your details are used only to get back to you. Privacy policy

Call +972-3-3801180Get in touch