All business manuals · Download PDF manual and fillable forms

AIT Technology · Practical implementation manual

Cybersecurity operations manual for businesses

A practical operating framework with department responsibilities, sector adaptations, everyday controls and incident playbooks. Customise it to the way your organisation actually works.

Version 1.0 · Published and sources checked

For: Owners, managers, department leads and the people responsible for IT. UK business context; specialist and regulated environments need additional assessment.

Illustration of colleagues working together on a documented business process
AI-generated editorial illustration. Fictional people and systems; no real customer information.

The process at a glance

Use these stages as a visual route through the work. Detailed actions, decision owners and exit checks follow in the procedures.

  1. Prepare and assign owners
  2. Identify and report
  3. Contain safely
  4. Assess and recover
  5. Learn and improve

A handoff requires a named owner and a recorded result. If a safety, data-access or approval condition is not met, pause the affected action and escalate.

Operating framework

1. Approve a company-specific version

This is a comprehensive starting framework, not a completed policy for an unidentified business. The owner must approve a named version covering the actual legal entities, sites, systems, suppliers, working hours and services. Identify exclusions and existing contractual obligations. Give each control a responsible person, deputy, review date and evidence location.

AIT Technology can tailor this manual to your company, departments and operating scenarios, and help implement bespoke workflows, integrations and software. Begin with discovery and agree the scope, responsibilities, acceptance tests and support arrangements. This publication does not promise certification, legal compliance, specialist forensic services or round-the-clock incident response.

2. Name decision-makers before an incident

The business owner is accountable for risk and approves exceptional expenditure and service restoration. The incident lead coordinates decisions and the incident log. IT carries out authorised technical containment and recovery. Department leads manage safe workarounds. The privacy lead assesses personal-data implications. Finance contacts the bank for suspected payment fraud. One communications owner approves customer and supplier updates.

Small companies may combine these roles, but must still name deputies and separate approval from execution where practical. Keep an offline contact sheet with trusted provider and bank contact routes. Never put passwords, recovery codes or API keys in the manual. Agree who can temporarily disable an account or suspend a service, including out of hours.

3. Map what must keep working

List email, identity, finance, files, website, customer records, operational equipment and supplier services. For each, record business owner, technical contact, critical data, integrations, recovery dependencies and maximum tolerable interruption. Agree recovery-time and acceptable-data-loss objectives with the business; a backup schedule alone does not establish either.

Classify information as public, internal, confidential or restricted using your own definitions. Record where sensitive information is stored and who needs access. Keep access and retention decisions consistent across file shares, email, backups and SaaS services. Prioritise a few critical workflows instead of treating every laptop and document as equally urgent.

4. Establish the everyday security baseline

Maintain named user accounts, least privilege, stronger sign-in protection where supported, approved password storage, managed devices, supported software and a documented update process. Separate everyday and administrator access. Review changes when people join, move roles or leave. Secure recovery methods and test an emergency access route without sharing credentials.

Keep backups protected from routine user compromise, including an offline or otherwise isolated copy where appropriate to the service. Set retention and recovery targets, monitor failed jobs and test restoration. Cloud synchronisation and recycle bins are useful features but should not be assumed to meet your recovery requirements.

Keep a register of internet-facing services and supplier connections. Remove unneeded access; restrict remote administration and record authorised changes. Protect logs from ordinary modification, limit sensitive content and decide who reviews alerts. Technical settings depend on your actual products and should be tested before rollout.

5. Run a proportionate control calendar

Daily or each working shift: review critical security alerts, failed backup jobs, unusual privileged access and payment-change requests. Weekly: review unresolved vulnerabilities, failed updates, stale incidents and restore-test actions. These are suggested operating frequencies; adjust to risk, coverage and contractual requirements.

Monthly: review privileged accounts, external sharing, suppliers with access and expiring exceptions. Quarterly: restore a representative service and rehearse an incident with its business owner. At least annually and after material change: review the risk register, business continuity plan, training and this manual. Record evidence and overdue actions rather than simply ticking “done”.

6. Handle incidents and reporting decisions

Treat suspected account takeover, ransomware, significant data exposure, payment fraud or safety-related disruption as urgent. Start a timeline, assign the incident lead and use a trusted communication channel. Distinguish confirmed facts from hypotheses. Preserve relevant logs and messages with access controls; do not upload an evidence dump to a public chatbot.

For a UK personal-data breach, the responsible privacy lead must assess risk promptly. ICO guidance says report notifiable breaches without undue delay and, where feasible, within 72 hours of becoming aware. Where a breach is likely to result in high risk to people, notification to affected people is also generally required without undue delay, subject to applicable conditions and exceptions. Record the decision and reasons even when not reporting. Do not wait for a complete forensic report before assessing deadlines. Check sector, contractual and overseas obligations with qualified advice.

Do not assume every IT outage is a reportable personal-data breach, or that every breach can wait 72 hours. A processor should inform its controller without undue delay. Use current ICO guidance for the organisation’s actual role. Do not claim the incident is resolved until recovery, access and business validation are documented.

7. Plan the first 30, 60 and 90 days

Days 1–30: approve owners, inventory critical services, close obvious access gaps, verify backups, publish the reporting route and rehearse one scenario. Days 31–60: implement joiner/mover/leaver and supplier controls, test restore dependencies, address prioritised vulnerabilities and validate safe workarounds. Days 61–90: rehearse cross-department response, measure overdue actions, improve alert coverage and approve the next risk-treatment plan.

Track restore tests passed, time to disable departed-user access, overdue critical findings, incident acknowledgement and recovery against agreed objectives. Training attendance alone does not demonstrate safe behaviour. AIT can help build a company-specific control dashboard and approval process; agree its inputs and access before connecting production systems.

Department responsibilities

Assign actual names and deputies to these roles. Combining roles in a small company does not remove accountability or the need for review.

Ownership, routine work, escalation and evidence
Department / ownerRoutineEscalate whenKeep a record
Leadership and managementManaging director / risk ownerApprove risks, funding, accountable owners and accepted exceptions; review unresolved high-impact findings.Major disruption, suspected data theft, fraud, safety impact or inability to recover.Risk register, decisions, delegated authority and review minutes.
IT and administrationIT lead / managed service ownerManage identity, patches, backups, configurations, asset inventory and alert review; test authorised changes.Unusual privileged activity, active exploitation, backup failure or loss of visibility.Change tickets, access reviews, restore results and protected event logs.
Finance and procurementFinance leadVerify supplier bank changes independently, separate payment approval and maintain trusted supplier contacts.Unexpected payment, urgent account-change request or suspicious executive instruction.Verification notes, approvals and bank incident reference.
HR and peopleHR lead with line managerNotify IT of starters, role changes and departures; protect personnel files and deliver role-specific training.Unplanned departure, inappropriate personnel access or suspected identity misuse.Authorised access requests, completion confirmation and training actions.
Sales and customer serviceCommercial / service leadUse approved CRM and sharing routes, verify unusual customer requests and minimise exports.Customer data sent incorrectly, fraudulent request or suspicious bulk export.Case notes, disclosure decision and approved customer communication.
Operations and productionOperations / site leadMaintain safe manual workarounds, controlled device use, supplier-access windows and critical-service recovery priorities.Unsafe equipment behaviour, loss of dispatch/control systems or unknown remote access.Shift log, workaround approvals, reconciliation and restart sign-off.
Marketing and websiteMarketing / website ownerControl publishing and domain accounts, check approved integrations and record website changes.Unexpected redirect, false content, lost domain control or exposed enquiry data.Publishing approval, version history, access records and recovery proof.
Privacy, legal and suppliersDesignated privacy / contract leadReview data-processing arrangements, supplier access, retention and breach-reporting duties.Possible personal-data breach, supplier incident or missed contractual notification.Assessment, reporting decision, supplier correspondence and action log.

Adapt the manual to your type of business

These are planning scenarios, not assessments of particular organisations. Add sector-specific duties, contractual requirements and safety expertise before adoption.

Retail and e-commerce

Protect or improve: Storefront, customer accounts, order records, payment-provider connections and refunds.

Example scenario: An administrator account changes checkout links.

Tailor the process: Separate publishing/refund rights; preserve a clean site version; verify payment-provider settings. Assess applicable payment obligations with the provider.

Manufacturing

Protect or improve: Production availability, engineering files, machinery support and safe restart.

Example scenario: An office compromise reaches a production-support workstation.

Tailor the process: Map IT/OT boundaries with competent engineers; control supplier access; do not scan, patch or disconnect machinery without safety review.

Warehousing and logistics

Protect or improve: WMS, labels, handhelds, dispatch interfaces and traceability.

Example scenario: Dispatch software is unavailable during a busy shift.

Tailor the process: Approve a minimal offline dispatch process and reconcile every temporary shipment record after recovery; protect labels and customer addresses.

Professional services

Protect or improve: Client confidentiality, document sharing, billing and delegated access.

Example scenario: A confidential client folder is shared externally.

Tailor the process: Review links and client boundaries; use restricted matter/project folders and confirm who can approve external disclosure.

Care and health-related businesses

Protect or improve: Sensitive records, appointment continuity and safe delivery of care.

Example scenario: A scheduling service outage affects visits.

Tailor the process: Agree safe fallback and welfare escalation with the responsible care lead. Specialist health, safeguarding and sector obligations require additional assessment.

Construction and field services

Protect or improve: Mobile devices, contractor access, drawings and supplier payments.

Example scenario: A technician loses a phone containing job information.

Tailor the process: Use managed access, minimal offline data and a tested lost-device process; keep current drawings available through controlled routes.

Hospitality

Protect or improve: Booking systems, guest information, tills and staff turnover.

Example scenario: Guest Wi-Fi shares access with a business device network.

Tailor the process: Separate guest and business services, review temporary staff access and arrange a safe booking/till fallback with providers.

Education and training

Protect or improve: Learner information, shared devices, safeguarding and continuity of teaching.

Example scenario: An account exposes a learner document set.

Tailor the process: Separate staff/learner permissions, minimise shared-device persistence and involve the safeguarding/privacy leads where relevant.

Charities and community organisations

Protect or improve: Donor and beneficiary data, volunteer access and donation accounts.

Example scenario: A volunteer retains access after leaving.

Tailor the process: Assign an owner for each platform, expire temporary access and verify changes to donation destinations through two trusted people.

Software and digital agencies

Protect or improve: Source code, secrets, deployment pipelines and customer environments.

Example scenario: A repository or build credential is exposed.

Tailor the process: Revoke and rotate credentials, assess use and affected deployments, protect CI/CD access and separate customer environments.

Remote and hybrid teams

Protect or improve: Identity, laptops, home networks, cloud sharing and remote support.

Example scenario: A fake helpdesk call persuades a user to install remote access.

Tailor the process: Publish a trusted support-verification route; restrict remote tools and test response when the user is away from an office.

Multi-site SMEs

Protect or improve: Consistent identity, local ownership, WAN dependencies and cross-site recovery.

Example scenario: One site loses connectivity while central systems remain healthy.

Tailor the process: Give each site a deputy and safe offline procedure, define local versus central incident authority and test inter-site dependencies.

Step-by-step procedures

Use only within the approved company scope. Timescales, technical commands, contact details and escalation authority must be completed for your environment. The completion check is an evidence requirement, not a tick-box guarantee.

Procedure 01

Joiner, role change and leaver

Accountable owner
Line manager + HR + IT
Start when
A person starts, changes duties or leaves.
  1. Manager requests named role-based access and an end date for temporary rights.
  2. IT grants minimum approved access; deliver sign-in and reporting guidance.
  3. On role change, remove superseded rights as well as adding new rights.
  4. On departure, disable access at the agreed time, revoke active sessions/tokens where supported, transfer ownership and recover devices.
  5. Check shared accounts, supplier portals, delegated mail and recovery contacts.

Evidence: Approved request and timestamped completion checklist.

Completion / handoff: Manager confirms retained business records and removal of unnecessary access.

Procedure 02

Phishing or suspicious message

Accountable owner
User + IT triage lead
Start when
Unexpected link, attachment, credential request or urgent instruction.
  1. Do not open, reply or forward attachments to colleagues; report by the approved route.
  2. Verify the request using an independently known channel.
  3. Tell IT whether any link was opened, data entered or file executed.
  4. IT preserves relevant evidence and checks related users/messages; contain affected access if indicated.
  5. Use the relevant takeover, malware or fraud playbook if activity occurred.

Evidence: Message reference, time and actions actually taken; handle content as untrusted.

Completion / handoff: Scope reviewed, affected people advised and protective actions verified.

Procedure 03

Suspected account takeover

Accountable owner
IT incident lead
Start when
Unrecognised sign-in, new MFA method, forwarding rule or sent message.
  1. Use a trusted device and contact route; assign the incident lead.
  2. Preserve relevant identity/mail audit information.
  3. Restrict affected access, revoke sessions/tokens and reset credentials through approved recovery.
  4. Review MFA methods, recovery details, forwarding rules, delegated access and connected applications.
  5. Assess downstream services and data exposure; restore only after validating the trusted account state.

Evidence: Audit timeline, access changes, affected services and privacy assessment.

Completion / handoff: IT and account owner confirm controlled access and follow-up monitoring.

Procedure 04

Malware or ransomware

Accountable owner
Incident lead + IT; site safety lead where relevant
Start when
Encryption notice, malicious execution or multiple unusable systems.
  1. Stop using the affected device; contact the incident team through a trusted channel.
  2. IT isolates affected endpoints/network access using approved controls. For operational equipment, coordinate safety before intervention.
  3. Do not wipe, reinstall or power-cycle systems as an improvised fix; follow specialist direction and preserve evidence.
  4. Identify scope, access path and backup integrity. Engage qualified response support when needed.
  5. Recover into a clean controlled environment, validate service/data and monitor before reconnection. Do not negotiate or pay a demand under this general manual.

Evidence: Incident timeline, containment decisions, clean restore tests and business sign-off.

Completion / handoff: Cause addressed sufficiently for safe operation; restored data and access validated.

Procedure 05

Supplier payment change or fraud

Accountable owner
Finance lead
Start when
Changed bank details, suspicious payment or urgent executive request.
  1. Pause the change/payment pending independent verification.
  2. Call an established supplier contact using trusted records, not details in the message.
  3. Record verification and separate approval where practical.
  4. If funds may have gone to an attacker, contact the bank immediately through a trusted route and preserve records.
  5. Assess account compromise and reporting obligations with the incident/privacy leads.

Evidence: Verification notes, approver and bank reference; no credentials in the log.

Completion / handoff: Payment destination confirmed or blocked and investigation/recovery actions assigned.

Procedure 06

Lost or stolen device

Accountable owner
User + IT + privacy lead
Start when
Missing laptop, phone, removable media or printed sensitive material.
  1. Report promptly, including last known possession and likely data/access.
  2. IT restricts access and invokes managed lock/wipe only under the approved process.
  3. Assess encryption, session state, stored data and downstream access; do not assume encryption settles the whole risk.
  4. Preserve management records and assess personal-data implications.
  5. Replace/re-enrol safely and validate removal of old device trust.

Evidence: Device identifier, times, management actions and risk assessment.

Completion / handoff: Access controlled, reporting assessed and replacement authorised.

Procedure 07

Accidental data disclosure

Accountable owner
Privacy lead + data owner + IT
Start when
Wrong recipient, exposed sharing link or unapproved upload.
  1. Report immediately; do not conceal the mistake or send further sensitive information.
  2. Remove inappropriate access where possible and preserve evidence of what was exposed.
  3. Establish data types, recipients, exposure window and whether access occurred.
  4. Assess risk and reporting deadlines; ask for secure deletion through an approved route without assuming a request proves deletion.
  5. Correct sharing controls and support affected people as appropriate.

Evidence: Disclosure record, assessment, notification decisions and mitigation.

Completion / handoff: Exposure contained, responsibilities discharged and corrective actions assigned.

Procedure 08

Critical service or supplier outage

Accountable owner
Service owner + incident lead
Start when
Email, SaaS, network or operational service is unavailable.
  1. Confirm impact and check official supplier status using a trusted route.
  2. Activate the approved manual/alternative process; avoid duplicate orders and unsafe shortcuts.
  3. Keep a minimum reconciliation record and give users factual updates.
  4. Coordinate supplier recovery and validate restored service with a representative workflow.
  5. Reconcile temporary records and confirm that access/logging protections remain active.

Evidence: Impact, supplier references, workaround transactions and validation.

Completion / handoff: Business owner accepts service and reconciled backlog.

Procedure 09

Website or domain compromise

Accountable owner
Website owner + IT
Start when
Unexpected redirects, content, DNS changes or lost publishing access.
  1. Escalate and preserve hosting/domain audit records.
  2. Restrict compromised access and coordinate with the registrar/host through trusted support.
  3. Where needed, suspend affected content through the authorised owner; retain clean backups.
  4. Review integrations, secrets, customer forms and possible exposure.
  5. Restore a verified version, rotate affected credentials and test public routes and enquiry handling.

Evidence: Affected URLs, change history, recovery version and tests.

Completion / handoff: Domain/site control verified and user impact assessed.

Procedure 10

Supplier remote-access request

Accountable owner
System owner + IT; operations approval for machinery
Start when
Vendor requests remote access or elevated permissions.
  1. Verify identity, purpose, target, time window and contract scope.
  2. Approve named least-privilege access; avoid shared permanent admin credentials.
  3. Record the session or relevant audit events consistent with privacy obligations.
  4. Monitor agreed work, review changes and revoke temporary access at completion.
  5. Validate the business system and record exceptions.

Evidence: Access approval, session/change reference and revocation confirmation.

Completion / handoff: Owner accepts work and temporary rights are removed.

Procedure 11

Patch and configuration change

Accountable owner
IT change owner + business service owner
Start when
Security update, exposed weakness or planned configuration change.
  1. Identify affected assets, exploit risk and business impact.
  2. Assign priority and deadline based on actual exposure; urgent exploitation may need accelerated action.
  3. Prepare backup/rollback and test on representative systems; include OT safety constraints.
  4. Approve and deploy in a controlled window with status monitoring.
  5. Verify installation, access and application behaviour; document residual risk or failure.

Evidence: Change record, approval, version/setting verification and rollback readiness.

Completion / handoff: Security objective and business function verified or rollback completed.

Procedure 12

Restore test and business recovery

Accountable owner
IT restore lead + process owner
Start when
Scheduled test or incident recovery authorisation.
  1. Choose a representative dataset/service and define success without overwriting production.
  2. Check dependencies and retrieve an authorised backup into an isolated test location.
  3. Validate integrity, access restrictions and business transactions with the data owner.
  4. Measure achieved recovery time and data gap against agreed objectives.
  5. Protect/delete test copies appropriately; fix failed dependencies and schedule retest.

Evidence: Backup reference, restore timestamps, tests and owner approval.

Completion / handoff: Objective met with evidence, or failure tracked with a named action and retest.

Records and templates to customise

Copy these field sets into your approved ticketing, document or workflow system. A record should have a named owner, access restrictions, retention and a review date. Store evidence by reference; do not paste secrets into forms.

Company approval and emergency contacts

Company / sites / scope / version / accountable owner / deputy / approval date / next review / trusted IT, bank, supplier and privacy contact routes / out-of-hours authority. Do not include passwords or recovery codes.

Asset and risk record

Service / business process / owner / data class / dependencies / supplier / impact / recovery-time objective / acceptable data loss / controls / remaining risk / decision owner / review date.

Incident log

Incident ID / detected time and time zone / reporter / confirmed facts / uncertain facts / affected systems and people / safety impact / lead / evidence references / action and approver / timestamp / next update / reporting assessment / closure sign-off.

Change or access approval

Requester / purpose / target / rights or change / start and expiry / risk / business approver / technical executor / test / rollback / completion and revocation time.

Restore and exercise result

Scenario / backup or dataset reference / test environment / expected result / achieved restore time and data gap / access checks / business validation / failures / owner / deadline / retest date.

Suggested incident prioritisation

  • Urgent: ongoing compromise, suspected sensitive-data exposure, fraud, safety risk or loss of a critical process. Contact the named lead immediately through a trusted route.
  • Significant: contained disruption or a material weakness requiring coordinated action. Assign an owner and agreed response deadline.
  • Routine: low-impact issues and improvement requests. Track to closure and escalate if scope changes.

Define company response times and cover explicitly. This manual and AIT's contact form are not emergency response services.

AIT Technology can build a version that fits your company

We can work with you to map existing processes, tailor departmental procedures, configure agreed controls and create custom software or integrations where standard tools leave a gap. Potential deliverables include onboarding workflows, access-approval forms, incident registers, AI review queues, operational dashboards and controlled connections between existing systems.

  1. Discover: understand your business, departments, systems and risks.
  2. Design: agree scope, owners, information boundaries and acceptance tests.
  3. Implement: configure or build the agreed solution with controlled access and a rollback plan.
  4. Validate: test representative scenarios, train named users and hand over documentation.
  5. Maintain: agree ownership, review cadence and any support service separately.

We confirm suitability, specialist needs, licence costs and delivery scope before commitments. No universal price, compliance certification, 24/7 coverage or guaranteed business result is implied.

Talk about your company's requirements

Sources, limitations and maintenance

This is original AIT implementation guidance informed by the public sources below, checked 18 November 2026. The role assignments, templates, frequencies and sample workflows are proposed operational designs to customise; they are not verbatim official requirements. Linked guidance may change. Review the company version after incidents, service/model changes, new legal obligations and at its agreed review date.

Regulated, safety-critical, clinical, payment and consequential decisions require appropriate specialist assessment. A general manual does not replace that work.

Explore the other business manuals · Read our latest articles

Download your ready-to-use pack

Branded covers, company footer and interactive forms. Use a PDF reader supporting AcroForms, save locally and reopen to check your entries. Browser support varies. The files do not send completed records to AIT.

Download manual (PDF)

Download fillable forms (PDF)

Download all three manuals and form packs (ZIP)