Bacchus Security

System security and hardening

An administrator account left behind after a departure or an old service still running after a migration creates avoidable exposure. Hardening starts with understanding what each system actually needs to do.

Design example

Give a contractor access to the machine they came to service.

A technician needs to adjust one machine. We define what they can reach and arrange for access to expire when the work is complete.

Contractor account
  • Assigned machineTime-limited access
  • Other machinesAccess blocked

When to get in touch

  • Elevated permissions pass between colleagues without a regular review.
  • Systems doing the same job have different security settings.
  • Alerts arrive without a clear procedure for assessing them.

Scope of work

  • An access matrix and rules for granting, changing and revoking access.
  • A configuration baseline suited to each system’s role.
  • A set of monitoring events with instructions for investigating them.

Our approach to the work

Before changing a permission, we check what the account holder needs to do, such as running a month-end close. We test the change with a limited group and prepare a rollback before applying it more widely.

Limit what a contractor can reach

What you gain

Permissions become easier to justify, and a documented baseline gives you a reference for spotting changes over time.

Discuss system security