Security is everyone’s second job. Give it one owner.
- A fractional security and compliance officer owns your program and its dates, working beside your IT team or MSP.
- Every contract clause, questionnaire and insurance renewal goes on one dated plan, reviewed with you each month.
- Changes are made in Microsoft 365 and Azure, not just recommended, and the evidence is kept as you go.
200+ Microsoft 365 and Azure tenants. 100+ engagements. 20+ years in regulated technology.
Who you get, and how the retainer runs
Your point of contact is a senior security and compliance lead who also directs the engineering in Microsoft 365 and Azure, so the plan and the changes stay connected.
- Your contact
- One named person for the program, from the first call onward.
- Works with
- Your IT team or MSP, and the leaders who make decisions on risk, budget and contracts.
- How we meet
- Calls and shared documents.
- Cadence
- A program review each month, a summary for leadership each quarter, and questionnaires or insurer questions as they arrive.
- Scope and hours
- Retainers start at 10 hours a month, and most run between 20 and 140 hours a month. The hours are agreed in writing before work starts, based on your obligations and their dates, and change with them.
- Frameworks
- CMMC, NIST SP 800-171, NIST CSF 2.0, NIST SP 800-53, SOC 2, ISO 27001, HIPAA aligned safeguards and HITRUST.
Signs nobody owns the program yet
If two or more of these sound familiar, the program needs an owner.
- Security questions land on whoever answered the last one.
- Contracts, questionnaires and renewals each bring their own date, and nobody keeps the list.
- Your IT team or MSP keeps things running, but nobody owns the program.
- Leadership asked who is accountable for security, and the answer was a pause.
What usually starts the conversation
“Who is accountable for security, and what is the plan?”
They want one name and a plan with dates. The first 90 days produce both.
“This agreement adds security terms we have to keep.”
Signing is only the start. Someone has to own each term, its date and its evidence for the life of the contract.
“That request is outside our scope.”
Fair enough. Running IT and owning security are different jobs. Your MSP keeps the first, and the officer takes the second.
The first 90 days, as an example
A general example, not a fixed schedule. Your plan is set with you, around your own dates.
-
Learn
Example timing Days 1 to 30
- Who owns what today
- Every obligation and its date
- A baseline of your Microsoft 365 and Azure settings
-
Plan
Example timing Days 31 to 60
- A ranked risk register
- A roadmap with owners and dates
- Policies that are missing or stale, drafted or updated
-
Run
Example timing Days 61 to 90
- First fixes made in the tenant
- The monthly review started
- The first summary for leadership
When nothing outside sets a framework, we use NIST CSF 2.0 as the program’s structure, starting with its Govern function.
After the first 90 days
- Each month
-
- Program review with your IT lead or MSP
- The risk register updated
- Obligations and dates checked, with a dated list of what is due next
- Tenant changes checked against the plan, with notes on what changed and why
- As requests arrive
-
- Questionnaires and insurer questions answered, with the evidence attached
- Each quarter
-
- A one page summary for leadership or the board, and a review of the roadmap
What we need from your side
A leader who can make decisions on risk and budget, admin access agreed with your IT team or MSP, copies of the contracts, questionnaires and policies you already have, and time for the monthly review.
The officer owns the program. Your team keeps running IT.
The split we agree at the start, so nobody wonders whose job something is.
| Area | Your officer | Your IT team or MSP |
|---|---|---|
| Security program and roadmap | Owns | Contributes |
| Risk register | Owns | Flags new risks |
| Policies | Writes and maintains | Reviews for fit |
| Identity and access design | Designs and approves | Builds and runs |
| Questionnaires and audits | Leads | Supplies evidence |
| Help desk and daily changes | Not involved | Owns |
What the program produces
Three documents you would see every month or quarter. Each one is a sample format with illustrative content, not a client’s document.
Risk register
Each risk ranked, with a plan, an owner and a status. Reviewed every month.
Risk register, excerpt
Sample format, illustrative content
| Risk | Rank | Plan | Owner | Status |
|---|---|---|---|---|
| R-03 Admin accounts can sign in with a code sent by text | High | Move admins to phishing resistant sign in, enforced by Conditional Access | IT lead | In progress |
| R-07 Nobody has tested a restore of SharePoint and OneDrive data | High | Run a restore test each quarter and keep the record | MSP | Open |
| R-09 Former staff still listed as guests in Teams | Medium | Remove them, then review guests every quarter | IT lead | Closed |
| R-11 Security terms in customer contracts are not tracked | Medium | Add each term to the obligations calendar with an owner and a date | Security officer | Closed |
Obligations calendar
Every date that someone outside can hold you to, in one list.
Obligations calendar, next quarter
Sample format, illustrative content
- January 20
- Customer security questionnaire dueOfficer leads, IT supplies evidence
- January 31
- Quarterly review of admin rolesIT lead, checked by the officer
- February
- Annual review of the policy setOfficer, approved by leadership
- March 1
- Cyber insurance renewal applicationOfficer prepares, your executive signs
Quarterly leadership summary
One page for leadership or the board: where things stand and what needs a decision.
Security program summary
Sample format, illustrative content
Quarter ending September 30
- Since last quarter
- MFA enforced for all users. Guest access cleaned up. Two policies updated.
- Top risks
- R-03 admin sign in, and R-07 untested restores
- Due next quarter
- A customer questionnaire, the policy review and the insurance renewal
- Decision needed
- Approve the license change for keeping audit logs longer than 180 days
Work we have delivered
Real engagements, described without naming the clients.
-
Defense, CMMC Level 2
One defense contractor started with a four week gap assessment that scored all 110 NIST SP 800-171 requirements. It passed its CMMC Level 2 C3PAO assessment with every requirement met.
-
Defense, plan of action
A Level 2 POA&M that an Air Force Research Laboratory program office accepted as the basis for releasing CUI.
-
Healthcare
Healthcare clients carried through HITRUST e1 and i1.
-
Incident response
A full Microsoft 365 incident response after an adversary in the middle (AiTM) session token theft.
Who this is for, and who it is not for
A good fit
- Organizations on Microsoft 365 and Azure with obligations and nobody who owns them.
- IT teams and MSPs that need security leadership without a full time hire.
- Firms that must stay ready between audits, renewals and customer reviews.
Not a fit
- You need help desk or day to day IT support.
- You want a report and no changes in the tenant.
- You need someone on site every day. We work by call and shared documents.
- You need legal advice on a contract. We tell you what a security term asks of your environment, and your counsel reads the contract.
Not sure which framework applies to you? Take the Starting Point check
Questions before you book
Who exactly is our officer?
Your point of contact is a senior security and compliance lead who also directs the engineering in Microsoft 365 and Azure. You deal with the same person each month, so the plan and the changes stay connected.
How many hours a month do we get?
Retainers start at 10 hours a month, and most run between 20 and 140 hours a month. We agree the hours and the monthly cadence in writing before work starts, based on your obligations and their dates. If those change, for example a new contract or a customer audit, we adjust the scope with you.
How is this different from a full time hire?
You get a security officer for the hours your program needs now, with Microsoft 365 and Azure engineering behind it. If you later hire full time, the program, register and evidence are documented, so that person starts from a plan.
Do you work with our MSP?
Yes. Your MSP keeps running day to day IT. We own the security program, design the changes and check the evidence. The table above shows the split.
What happens if we have an incident?
Call your officer. We work the Microsoft 365 side with your IT team or MSP, keep a record of what happened and what was done, and bring in the people who decide on notices, such as your counsel and your insurer. How fast we respond is agreed in the retainer.
We have run a full Microsoft 365 incident response after an adversary in the middle (AiTM) session token theft.
Can you sign questionnaires or attestations for us?
We prepare the answers and attach the evidence. A named person in your organization signs, because the attestation is your organization’s statement.
Which frameworks do you cover?
CMMC, NIST SP 800-171, NIST CSF 2.0, NIST SP 800-53, SOC 2, ISO 27001, HIPAA aligned safeguards and HITRUST.
How is the work priced?
As a retainer, with the scope and cadence agreed in writing before work starts. Fixed scope projects, such as a gap assessment, can run alongside it.
What happens after you book
- Pick a 30 minute time that suits you.
- We talk through your obligations, your dates and who does what today.
- You leave knowing whether a fractional officer fits, and what the first 90 days would cover.
Bring the obligations nobody owns yet to a 30 minute call.
You leave knowing where you stand, what the first 90 days would cover and what comes next.