Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Windows · Linux · Laptops · Servers

Operating System Build Security Review

Your standard laptop and server builds are copied hundreds of times, and so are their weaknesses. We review them for insecure services, permissions, unnecessary features and privilege escalation paths.

  • Windows and Linux
  • CIS Benchmarks
  • Privilege escalation paths
Sample findings · Laptop build reviewSample
CRITICALAny user can become a local administratorA service runs from a folder users can write to
HIGHDisk encryption can be bypassed at bootNo pre-boot authentication
HIGHSame local admin password on every laptopOne compromise opens the whole fleet
MEDIUMOutdated scripting runtime installed by defaultNot needed by any business application
Each finding with evidence, a risk rating and a fixSample findings

In one sentence

What is an operating system build review?

An operating system build review examines your standard Windows, Linux or other builds for deviations from hardening best practice, insecure services, misconfigured permissions, unnecessary features and paths that let a user or attacker gain more control.

We review the build as it is configured and test it as a user would use it, so you see both the configuration gaps and what an attacker could actually do with them.

Builds we review

  • Employee laptops and desktops
  • Virtual desktop images
  • Windows and Linux server templates
  • Kiosks and specialised devices

Scope

What we review

Everything on the build that an attacker with access to it could use.

Services and software

Installed software, running services and scheduled tasks that are unneeded, outdated or insecure.

  • Services
  • Software
  • Tasks

Accounts and local privileges

Local accounts, administrator rights and shared credentials across devices.

  • Local admins
  • Credentials
  • Groups

Security controls

Disk encryption, firewall, endpoint protection, application control and their configuration.

  • Encryption
  • Firewall
  • EDR

Privilege escalation paths

File and service permissions, drivers and misconfigurations that let a user become administrator.

  • Permissions
  • Drivers
  • Misconfigurations

Patch level

Missing security updates in the operating system and installed software.

  • Updates
  • Versions
  • Exposure

Logging and auditing

Whether security-relevant events are recorded and kept.

  • Event logs
  • Auditing
  • Retention

Approach

How we review a build

Configuration review and hands-on testing together.

Step 1

Configuration review

We compare the build with hardening guidance such as the CIS Benchmarks.

Step 2

Hands-on testing

As a standard user, we try to escalate privileges and bypass security controls.

Step 3

Prioritised fixes

You receive the findings ranked by risk, with the setting or change that fixes each one.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we review against

So your builds meet the guidance your auditors expect.

  • CIS Benchmarks
  • Microsoft security baselines
  • NIST SP 800-53
  • ISO/IEC 27001

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

What do you need for a build review?
A device or virtual machine with your standard build, a standard user account and, for the configuration review, an administrator account or exported settings.
Do you review Windows and Linux?
Yes, and other operating systems on request. Tell us your platforms during scoping.
Is a build review the same as a vulnerability scan?
No. A scan lists missing patches. A build review also checks configuration and tests whether a user can actually escalate privileges or bypass controls.
How often should builds be reviewed?
Whenever the standard build changes significantly, and at least once a year.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.