Information Security Policy

How we run our information security management system (ISMS): who is responsible, how we assess and treat risk, the baseline controls we apply, and how clients can audit us.

1. Purpose and scope

This policy sets out how Carefully Coded Ltd ("we", "us") protects the confidentiality, integrity and availability of the information we handle. It is the top-level document of our information security management system (ISMS). The other security policies listed in section 13 sit beneath it.

The ISMS covers:

  • all work we do for clients, including web platforms, mobile apps, back-end services, databases and software for custom hardware such as displays and sensor stations;
  • equipment and software we install on client sites, including airports and other secure locations;
  • the company devices, accounts, cloud services and source code repositories we use to deliver that work;
  • everyone who works for us, including the director, employees and any contractors.

Our ISMS is aligned to the principles of ISO/IEC 27001 and to the UK National Cyber Security Centre's (NCSC) baseline technical controls.

Where a client contract sets a stricter requirement than this policy, the contract takes precedence for that client's work.

2. Our commitments

We will:

  • keep this ISMS documented, in force and up to date for the whole term of every client contract that requires it;
  • identify and manage information security risks in a consistent, recorded way;
  • apply our five baseline technical controls to every device and service in scope;
  • meet our legal duties, including the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018;
  • report and handle incidents promptly, as set out in our Incident and Data Breach Response Procedure;
  • give clients the evidence they need to check that we are doing what we say.

3. Roles and responsibilities

Role Who Responsibilities
ISMS owner and security lead Tom Emmerson, Director Accountable for information security. Approves policies, accepts risks, runs management review, leads incident response and is the contact for client audits.
Data protection lead Tom Emmerson, Director Oversees personal data handling. See our Data Protection Policy.
All staff and contractors Everyone who works for us Follow these policies, complete training, protect devices and accounts, and report incidents or concerns straight away.

Where duties cannot be fully separated, we record the decision and the director reviews it at the next management review. Security concerns can also be raised through our Whistleblowing Policy.

4. Risk assessment and treatment

We keep a risk register. For each risk we record the asset affected, the threat, the likelihood and impact (each scored 1 to 5), the overall score, the owner, the treatment and the target date.

We will:

  • review the whole register at least every 12 months;
  • assess new risks before starting any new project, client engagement, on-site installation or significant change to our systems;
  • treat each risk by reducing it with a control, avoiding it, transferring it (for example to a supplier or insurer) or accepting it;
  • only accept a risk scoring 15 or above with the director's written approval, recorded in the register.

5. Asset register

We keep an asset register listing our devices, cloud accounts and services, source code repositories, client data sets and hardware held for clients. Each entry has an owner, a classification and a location. We update the register when an asset is added, changed or disposed of, and check it in full at least every 12 months. Equipment installed on client sites is recorded against the client and site.

6. Baseline technical controls

We apply five baseline technical controls, based on NCSC guidance, to every device and service in scope.

6.1 Firewalls

  • Every device has its built-in firewall switched on.
  • Cloud services only expose the ports they need. Administrative interfaces are not open to the internet unless protected by multi-factor authentication (MFA) or restricted by IP address.
  • Default firewall and router passwords are changed before use.

6.2 Secure configuration

  • Unused software, accounts and services are removed or disabled.
  • Default passwords are changed before a device or service goes into use.
  • Auto-run is disabled and devices lock automatically when idle.
  • Hardware we supply to clients is configured to a documented build standard before installation.

6.3 User access control

  • Access follows least privilege and is removed promptly when no longer needed.
  • MFA is used on all systems holding client data, and everywhere else it is available.
  • Administrator accounts are separate from day-to-day accounts.

Full details are in our Access Control, Confidentiality and Training Policy.

6.4 Malware protection

  • Every device runs supported anti-malware protection that updates automatically.
  • Only software from trusted sources is installed.

6.5 Security update management

7. Supplier security

Before using a supplier that will store or access client data, we check its security and data protection position and record the result. We prefer suppliers with recognised security certifications such as ISO/IEC 27001 or SOC 2. We review key suppliers at least every 12 months. Our current list is in our Sub-processors page, and where data is stored is covered in our Data Location Policy. Our primary hosting is a UK region of a major cloud provider, agreed with each client in the contract.

9. Policy review

We review every ISMS policy at least every 12 months, and sooner after a significant incident, a major change to our services or systems, a change in law or a new client requirement. Each policy shows its version, owner, effective date and next review date.

10. Internal audit

At least every 12 months the director carries out an internal audit of the ISMS against this policy and its baseline technical controls. The audit checks a sample of records, including the risk register, asset register, access reviews, patching records, training records and the incident log. Findings and actions, with owners and due dates, are recorded and tracked to closure.

11. Management review

At least every 12 months the director holds a recorded management review covering audit findings, incidents, risk register changes, penetration test results, supplier reviews, certification progress and resources. The review produces dated actions.

12. Client audit rights and copies on request

Clients may audit our compliance with these policies as their contract allows. We will:

  • provide copies of any policy in this ISMS within 5 working days of a written request;
  • provide supporting evidence, such as risk register extracts, training records, patching records or penetration test summaries, within 10 working days of a written request, unless the contract sets a different timescale;
  • support on-site or remote audits at a mutually agreed time;
  • act on audit findings within the timescales agreed with the client.

Requests should be sent to info@carefully.codes.

13. Information security policy index

Policy Covers
Vulnerability Management, Patching and Secure Development Policy Patching timescales, secure development, change control and vulnerability disclosure
Penetration Testing Policy Independent testing, remediation and retesting
Incident and Data Breach Response Procedure Handling, reporting and learning from incidents
Business Continuity, Disaster Recovery and Backup Plan Backups, recovery objectives and continuity scenarios
Access Control, Confidentiality and Training Policy Access, MFA, joiners and leavers, training and device security
Organisation
Carefully Coded Ltd
Version
1.0
Owner
Tom Emmerson, Director
Effective from
19 November 2026
Next review
19 November 2027

Questions about this policy? Email info@carefully.codes.