Ongoing security operations
Watching new vulnerabilities, patching on a schedule and keeping access tidy, month after month.
A penetration test is a snapshot. The week after it, a new vulnerability is published in a library you use, an employee leaves with an SSH key, and a dependency alert sits unread. Security operations is the routine that catches those, on a schedule, with a written record.
What we look after
- Watching published vulnerabilities (CVEs) for the software and versions you actually run
- Read-only patch checks across your servers, with the exact update for each one that is behind
- Dependency alerts triaged by whether the vulnerable code is reachable, then fixed in order
- Access reviews: user accounts, SSH keys, API tokens and deploy keys that should be removed
- Security review of each new release of your mobile apps and web builds
- A first response plan for when something does go wrong
What do you get at the end?
- A monthly report: what was published that affects you, what was patched, what is still open
- An urgent notice when a vulnerability in your stack is being exploited in the wild
- Fix pull requests for dependency updates, tested before merge
How does the engagement run?
A written scope and the access you grant come first. After that, changes happen inside agreed windows and each one goes into a change log you keep a copy of.
Frequently asked questions
Is this a 24/7 security operations centre?
No. We do not run round-the-clock monitoring and do not claim to. This is scheduled work done during business hours, with urgent notices when a published vulnerability in your stack needs action sooner.
Do you change our servers?
Patch checks are read-only. Updates are applied by your team, or by us when you authorize each change in writing, and we confirm the result afterwards.
Tell us what you need looked after.
A short call, then a signed scope. No testing before that.