Skip to content
Talk to an engineer

Security & InfrastructureYou should hear about the outage from us, not from a customer.

Most organizations find out a server is down because somebody outside notices. The monitoring either does not exist or reports into a mailbox nobody opens, the firewall was configured once by whoever wired the office, and remote access grew out of whatever got people working from home in a hurry. This is the work of running that layer deliberately: the servers and the connection watched, the perimeter configured and maintained, access issued per person, and patches applied on a published cadence rather than after something breaks.

Talk about this

Commitments

Servers and connections, alerting to a person
Watched
Firewall rules written down and reviewed
Documented
Remote access issued and removed by name
Per person

Security and Infrastructure

We watch your servers and your connection for outages and deal with the problem before it grows. Alongside that we set up and run the equipment that keeps the network closed to everyone else: firewalls, antivirus and threat detection, and remote access for staff working away from the office.

Patching is part of it. Software updates and security fixes are applied as they are needed rather than whenever somebody gets to them.

When would I want this?

  • You want to reach your workspace securely from home
  • You want a defense that acts before an incident rather than after one
  • You want business practices that meet a standard
  • You want infrastructure that scales with little downtime
  • You want to keep your proprietary information from leaking

Sounds like

You might recognize one of these.

  • We found out the server had been down all weekend because a customer told us.

  • Staff working from home connect however they worked it out at the time.

  • Our firewall was set up by the company that wired the office and nobody has touched it since.

  • We are told we have to meet a standard, and we cannot say what we already have.

What you get

What lands on your side, and stays there.

  • Monitoring on every server and connection, alerting to a named person
  • A documented firewall configuration and a reviewed rule set
  • Managed threat detection on servers and network equipment
  • Remote access issued per person, with removal tied to leaving
  • A published patch cadence for infrastructure, and a record of what was applied

Shapes

How this usually runs.

  1. Infrastructure review

    1–2 weeks

    What is running, what is watching it, what the firewall allows, and how people reach the network from outside it.

  2. Remediation

    2–6 weeks

    Closing what the review found, in the order of what would hurt most, with each change written down.

  3. Managed infrastructure

    Ongoing

    Monitoring, perimeter, access and patching operated as a running service.

What this includes

The work, specifically.

Not every engagement needs all of it. This is the range we cover and what each part is actually for.

  • Monitoring and alerting

    Servers, connections and capacity watched continuously, with alerts routed to a named person on a rota rather than into a shared mailbox.

  • Firewall and perimeter

    A managed firewall with a written configuration and a rule set reviewed on a schedule, so the openings that were temporary at the time do not become permanent by default.

  • Threat detection

    Managed detection on servers and network equipment, tuned so an alert means something and monitored by somebody whose job it is.

  • Remote access

    Business VPN and conditional access issued per person and tied to the same joiner and leaver process as everything else, so access ends on the day employment does.

  • Infrastructure patching

    Operating system, firmware and appliance updates applied on a published cadence, with a record of what went on and when.

Tooling

What we build it with.

No tool here was picked because it was new. Where we do reach for something novel, it is in one place, for a stated reason, and it is written down.

Monitoring
  • Uptime and service monitoring
  • Capacity and disk alerting
  • On-call routing
Perimeter
  • Managed firewall
  • Network segmentation
  • DNS and content filtering
Access
  • Business VPN
  • Multi-factor authentication
  • Conditional access

Questions

Security, honestly.

  • That one is about the devices people carry and the data on them. This one is about the servers, the connection and the perimeter around them. Most organizations want both and the same team runs them, but they answer different questions and they fail in different ways: a laptop failure costs one person a day, a connection failure costs everybody one.

  • Having one and running one are different things. A rule set nobody has reviewed since installation collects openings that were temporary when they were made, and the record of why each one exists leaves with whoever made it. What you get here is a written configuration, a reviewed rule set and somebody who owns it.

  • This service puts the controls in place and produces the records an assessor asks to see, which is most of the work and none of the judgment. The assessment itself, and the engineering behind a framework such as CMMC, belongs to the cybersecurity division, where it is done by people who do it full time.

Often paired with

Next step

Tell us what’s breaking.

Forty-five minutes, no charge, no deck. We’ll tell you what we’d do, what it would likely cost to run, and where your estate is fine as it is.

Talk to an engineerSee how we work
Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.