Consulting and operating leadership

IT operations and cybersecurity services

From a specific project or problem to ongoing senior CIO or CISO leadership.

Principal-led. The person you speak with remains responsible for the engagement. Any client-team work or specialist contributions are defined in the scope.

Different ways to engage

Match the engagement to the work.

Specific projects, independent assessments, implementation leadership and fractional or interim leadership are separate ways to engage. You do not need to purchase one before another.

Find the work you need

Services by area

Choose a service to see what Plain Ops can do and what you receive.

01 / 05

Cybersecurity & Risk

4 services

Security program and control review

When this fits

Leadership wants to know whether its reported security coverage matches the controls actually in place.

What Plain Ops can do

Review the program, control ownership, existing evidence, and material gaps in coverage or validation.

What you receive

A findings report that separates confirmed gaps, assumptions and questions requiring more testing.

Scope

Not a certification, audit opinion or penetration test; if more testing is needed, the review identifies what to test and who should perform it.

Relevant frameworks: NIST CSF, CIS Controls

Vulnerability management

When this fits

Scans generate findings, but remediation is inconsistent, poorly prioritized, or nobody owns it.

What Plain Ops can do

Assess coverage and remediation workflows; establish prioritization, ownership, escalation and review practices.

What you receive

Clear remediation owners, a prioritized queue of fixes, an escalation process and reporting on remaining exposure.

Scope

Scanning-tool operation and hands-on remediation are included only when specifically agreed.

Identity and access governance

When this fits

Access rights, privileged accounts, or offboarding responsibilities are hard to establish and verify.

What Plain Ops can do

Review ownership, access lifecycle, exception handling, privileged access and available enforcement evidence.

What you receive

A list of access gaps, recommended changes and named owners for the decisions that follow.

Scope

Any changes to access systems or technical testing require agreed permissions and a clear assignment of who performs the work.

Security monitoring and incident readiness

When this fits

Security tools and providers generate alerts, but leadership cannot tell whether important activity is detected and acted upon.

What Plain Ops can do

Review monitoring coverage, MSSP responsibilities, escalation, response handoffs, and incident decision procedures.

What you receive

A list of monitoring gaps, unclear handoffs and specific response improvements or tests to pursue.

Scope

This is a review of monitoring and response readiness, not a managed security operations center or 24/7 response service.

02 / 05

Governance & Compliance

4 services

Audit and customer security review readiness

When this fits

An audit or customer questionnaire is approaching, but evidence is scattered or control ownership is unclear.

What Plain Ops can do

Organize requirements, validate available evidence, identify gaps and coordinate readiness actions.

What you receive

An evidence inventory, a list of what is missing and a preparation plan with named owners.

Scope

Your organization approves evidence submitted to customers or auditors; formal audit opinions remain with qualified assessors.

Relevant standards and requirements: SOC 2, HIPAA, PCI DSS, NYDFS

Policies, standards and operating procedures

When this fits

A required policy or process does not exist, is outdated, or is impossible for the team to follow consistently.

What Plain Ops can do

Develop or revise specific IT and security controls with clear operating responsibilities and approval routes.

What you receive

A draft policy, standard or procedure your team can review, approve and put into use.

Scope

Your organization approves and adopts the documents; legal interpretations stay with counsel.

Control ownership and evidence

When this fits

Management reports controls as operating, but cannot readily show who performs them or what proves they work.

What Plain Ops can do

Map controls to owners, workflows, evidence sources, review cadence and corrective actions.

What you receive

A record of who owns each control, what evidence should exist and where proof is missing.

Scope

The review identifies what the available evidence supports; it is not a formal audit opinion.

IT governance and change management

When this fits

Changes, priorities and technology decisions are inconsistent, poorly documented, or delayed in escalation.

What Plain Ops can do

Review decision and change paths; establish practical risk, approval, scheduling, release and follow-through practices.

What you receive

Change and decision procedures, named approval responsibilities and a regular review schedule.

Scope

Your authorized leaders approve production changes and accept risk unless that authority is expressly delegated.

Relevant governance framework: COBIT

03 / 05

IT Operations & Reliability

5 services

Incident and problem management

When this fits

The same outages recur, or incidents take too long to resolve.

What Plain Ops can do

Review incident response, service ownership, recurring causes and corrective-action practices, then help establish improvements.

What you receive

Updated incident and problem practices, assigned ownership and a prioritized plan to address repeat failures.

Scope

The scope sets whether Plain Ops designs the process, helps implement changes or leads the work; continuous incident response is separate.

Relevant framework: ITIL

Service desk and request management

When this fits

Tickets age, users escalate repeatedly, and the team struggles to control the queue.

What Plain Ops can do

Assess intake, routing, prioritization, knowledge use, measures and ownership; lead agreed process changes.

What you receive

Clearer ticket routing and queue rules, assigned owners and measures the service desk can track.

Scope

The work improves how your service desk operates; it does not provide replacement support-desk staffing.

Relevant framework: ITIL

ITSM process and ServiceNow/Jira workflows

When this fits

Service-management tools and processes do not reflect how work actually needs to move.

What Plain Ops can do

Review incident, request, change and service workflows; define improvements and lead the agreed implementation.

What you receive

Agreed workflow requirements and, when implementation is included, completed process changes or a plan with acceptance tests.

Scope

The scope identifies who handles custom development and integrations, including when specialist platform engineering is needed.

Relevant framework: ITIL

Asset and configuration management

When this fits

Equipment, applications and service dependencies are incomplete, stale or disputed.

What Plain Ops can do

Assess inventory/CMDB practices, service relationships, accountable sources and update processes.

What you receive

A reconciled view of the agreed assets and service relationships, with a plan to correct gaps and keep records current.

Scope

Inventory cleanup, automated discovery and integrations depend on the systems available and the implementation work agreed.

Vendor and MSP accountability

When this fits

Internal teams and providers disagree over who owns an outage, backlog, service level or promised change.

What Plain Ops can do

Review contracts, responsibilities, handoffs, escalation and performance evidence; establish workable operating reviews.

What you receive

An agreed division of responsibilities, escalation routes, acceptance criteria and measures for vendor reviews.

Scope

You retain vendor and contract decisions; renegotiation and legal work are agreed separately.

04 / 05

Architecture & Resilience

4 services

Infrastructure and architecture assessment

When this fits

Leaders need a defensible view of aging systems, technical risks, dependencies and operational maintainability.

What Plain Ops can do

Examine the current architecture, relevant inventories, lifecycle risks, ownership and major dependencies.

What you receive

A list of architecture risks, critical dependencies and the decisions that need attention first.

Scope

Live technical testing and system changes require separate authorization and an agreed implementation team.

Modernization planning

When this fits

A replacement or investment proposal is being made before costs, dependencies or business requirements are understood.

What Plain Ops can do

Establish requirements, baseline, options, operating consequences and a defensible sequence of investment.

What you receive

A sequenced modernization roadmap showing options, estimated costs, tradeoffs and decisions.

Scope

Cost estimates remain projections until validated; purchasing and deployment are separate decisions.

Disaster recovery planning and validation

When this fits

The recovery plan names objectives, but nobody can show whether the technology and responsibilities can achieve them.

What Plain Ops can do

Review recovery dependencies, roles, procedures, and evidence of prior tests; develop requirements for validation.

What you receive

Identified recovery gaps, updated procedures or runbooks and a plan for testing recovery.

Scope

A test plan does not prove recovery will work; any live restore or failover test requires separate authorization.

Business continuity readiness

When this fits

The organization needs defined continuity responsibilities, dependencies, response procedures or exercise preparation.

What Plain Ops can do

Structure the agreed continuity work, reconcile source material, identify decision owners and prepare plans and documents your team can use.

What you receive

The agreed continuity plans and supporting documents, open decisions and a clear handoff to their owners.

Scope

Your business owners make and approve continuity decisions; Plain Ops prepares and reconciles the supporting plans and documents.

05 / 05

Leadership & Execution

4 services

Fractional CIO or CISO leadership

When this fits

The company needs senior IT or security judgment and accountability, but does not require a full-time executive for the agreed remit.

What Plain Ops can do

Provide ongoing part-time leadership across priorities, risk, vendors, programs and executive decisions within a defined scope.

What you receive

Regular leadership reviews, decisions and follow-through across the responsibilities covered by the agreement.

Scope

You can engage CIO or CISO leadership separately; decision authority, availability and urgent-work coverage are agreed in writing.

Principal credentials: CISSP (Certified Information Systems Security Professional); ISSMP (Information Systems Security Management Professional); CGEIT (Certified in the Governance of Enterprise IT)

Interim IT or security leadership

When this fits

A departure, transition, acquisition or stabilization period has left a leadership responsibility uncovered.

What Plain Ops can do

Assume agreed temporary leadership responsibilities and support operating continuity and transition.

What you receive

Leadership coverage during the transition, with decisions handled and a clear handoff point.

Scope

The scope sets which decisions Plain Ops can make, how long the role lasts and who takes over.

Project and program execution

When this fits

A necessary operating change is understood, but decisions, capacity and coordination keep delaying it.

What Plain Ops can do

Lead the defined work across teams and vendors, establish priorities and drive accountability to the agreed completion state.

What you receive

The agreed changes put into use, or a clear handoff showing which changes are underway and who will finish them.

Scope

No assessment is needed when the required change is already understood; scope, duration and completion are agreed up front.

Operational stabilization

When this fits

Essential IT work has become reactive, priorities are unstable or management lacks an operating grip.

What Plain Ops can do

Assess the immediate operating conditions, establish practical ownership, prioritize urgent corrections and lead a defined stabilization effort.

What you receive

Clear priorities and owners, regular operating reviews and the agreed fixes underway or completed.

Scope

The assignment has an agreed stabilization goal, not open-ended responsibility for day-to-day IT operations.

For examples of prior operating work, see Work & Results. For audience-specific information, see CFOs and advisors or investors and operating partners.

Discuss the work you need done.

Bring a specific service, project, leadership need or recurring problem. The first conversation sets the scope.