Services
Three service lines for small regulated businesses: managed security, insurance and incident readiness, and automation. Every engagement is scoped on a call and quoted in writing.
Managed Security
Know what is exposed, what got fixed, and what to show the insurer
For accounting firms, law firms, medical practices, insurance agencies, financial institutions, and manufacturers (office IT only) that have devices nobody is watching. I work alongside your existing IT provider rather than replacing them.
Monitor
Read-only vulnerability scanning, attack surface monitoring, a monthly written posture report, and a review call to walk through it.
- Makes no changes to your endpoints
- Works alongside an existing IT provider
- Report written in plain language, with what I could not verify called out
Maintain
Remediation for what Monitor finds. A scheduled monthly patch window, an approved exception list for anything that cannot be patched yet, and a ticket raised on every failed fix.
- Patch window agreed with you and your IT provider
- Exceptions documented, not ignored
- Not sold on its own
Certify
Evidence for the insurer and the auditor, built from the Monitor and Maintain record so it reflects what is actually in place.
- Completed insurer questionnaire evidence pack
- Penetration test summary
- Framework mapping
- Cover letter signed under my CISSP
How a managed engagement starts
Every managed engagement begins with onboarding: agent deployment, a baseline scan, and a first remediation sprint to clear the backlog before the monthly cadence begins. You see the first posture report before the first monthly cycle.
Good to know
- Packages are sized by device count.
- Scanning starts only after written authorization and an agreed scope.
- Incident response is a separate engagement and is not included in Monitor, Maintain, or Certify.
- Software outside the approved catalog is not covered by Maintain. We agree on the catalog during onboarding.
Insurance and Incident Readiness
Answer the insurer with evidence, and know what happens on a bad day
Cyber insurance applications and renewals now ask for proof, not promises. These engagements produce the evidence and the plan, on a schedule that lines up with your renewal.
Cyber Insurance Readiness Assessment
Gap analysis against your actual insurer questionnaire, a remediation plan ordered by what the insurer weighs most, and an evidence package you can attach to the application.
Certify
An annual readiness engagement for clients who are not on managed security: questionnaire evidence pack, penetration test summary, framework mapping, and a cover letter signed under my CISSP.
Incident Response Package
Incident response plan development, a facilitated half-day tabletop exercise, and an after-action report. Available individually or together, with an annual refresh and re-run so the plan keeps up with the business.
Automation
Automation that handles sensitive data the way an auditor would expect
Manual processes that touch client records, invoices, or credentials are where errors and exposure pile up. I build the automation with least privilege, logging, and a human approval step wherever the stakes call for one.
Security Audit and Automation Plan
Process assessment, a security review of the systems involved, and a prioritized automation roadmap. The roadmap is based on your actual processes, not a template.
Pilot Automation Project
One to two processes automated end to end, training for the people who run them, and 30 days of support after go-live.
Zapier or Make to n8n Migration
Move existing workflows to self-hosted or managed n8n to cut recurring platform spend and keep your data on infrastructure you control.
Automation Retainer, Professional
Three to five processes, 90 days of support, and performance monitoring so you know each workflow is still running the way it did on day one.
Automation Retainer, Enterprise
Multi-system integration, custom dashboards, security monitoring of the automation workflows themselves, and compliance reporting.
Scope and tools
Retainers are scoped to a defined set of processes, agreed in the proposal. I work in n8n first, and with Make, Zapier, Airtable, and custom APIs when they are the right fit for what you already run.
Process
How engagements work
No prices on this site, because the right scope depends on your device count, your systems, and what the insurer is asking for. Here is the path from first contact to work starting.
-
1
Fit call
A 30-minute call to confirm the problem, the environment, and whether I am the right person for it.
-
2
Scoped written proposal
A proposal that names the scope, the deliverables, the schedule, and a fixed quote for that scope.
-
3
Signed agreement
We both sign. For managed security this includes written authorization and the agreed scope for scanning.
-
4
Work begins
Onboarding for managed security, or the build for automation, followed by ongoing reporting and support.
The BitForge security promise
I design for least privilege and audit logging from the start. Every credential an automation uses is scoped to the minimum it needs, every scan runs under written authorization, and every report tells you what I found in plain language, including what I could not verify. Security work is never finished, so I would rather show you the record than promise an outcome.
Not sure which service fits?
Start with the fit call. I will tell you which option matches the problem, or whether you need one at all.