Information Security Policy
Organisation | [Tessaract Analytics Ltd] |
Policy owner | [Name, Head of Information Security] |
Approved by | [Name, Chief Executive, on behalf of the Board] |
Version | [3.1] |
Effective date | [1 January 2027] |
Review date | [January 2028] |
Classification | [Internal] |
1. Purpose
[This policy sets out how Tessaract Analytics protects the confidentiality, integrity and availability of the information it holds for its customers, staff and partners. It supports our information security management system (ISMS), which is aligned with ISO/IEC 27001.]
2. Scope
[This policy applies to all employees, contractors, temporary staff and third parties who access Tessaract information or systems, and to all information in any form: digital, paper or spoken, on company or personal devices, in our offices, remotely or in the cloud.]
3. Policy statement
Tessaract Analytics will:
[Identify and manage information security risks to an acceptable level agreed by senior management.]
[Protect information according to its classification and legal, regulatory and contractual requirements.]
[Give people only the access they need for their role.]
[Train all staff to recognise and report security risks.]
[Detect, respond to and learn from security incidents.]
[Continually improve the ISMS and set measurable security objectives each year.]
4. Roles and responsibilities
Role | Responsibilities |
|---|---|
[Board / Chief Executive] | [Approve this policy and risk appetite; provide resources; receive security reporting quarterly] |
[Head of Information Security] | [Own the ISMS and this policy; maintain the risk register; coordinate incident response and audits] |
[IT Director] | [Implement technical controls; manage infrastructure, devices and identity] |
[Data Protection Officer] | [Advise on privacy law; handle personal data breaches and data subject requests] |
[Information asset owners] | [Classify their information, approve access, review access quarterly] |
[Line managers] | [Ensure their teams complete training and follow this policy; request leaver access removal] |
[All staff and contractors] | [Follow this policy, protect information, report incidents and weaknesses immediately] |
5. Risk management
[Information security risks are assessed at least annually and when significant changes occur, using the company risk methodology (likelihood × impact on a 5 × 5 scale).]
[Risks above the appetite threshold must have a treatment plan with an owner and target date.]
[Applicable controls and justifications for exclusions are recorded in the Statement of Applicability.]
6. Asset management and classification
[All information assets (data, systems, devices) are recorded in the asset register with an owner.]
Classification | Description | Examples | Handling |
|---|---|---|---|
Public | [Approved for public release] | [Marketing material, published reports] | [No restrictions] |
Internal | [For staff and authorised contractors] | [Policies, internal announcements] | [Not shared externally without approval] |
Confidential | [Could harm the company or customers if disclosed] | [Customer data, contracts, financials, source code] | [Access on need-to-know; encrypted in transit and at rest; shared only via approved tools] |
Restricted | [Severe harm if disclosed] | [Special-category personal data, credentials, encryption keys, M&A plans] | [Named individuals only; MFA; logged access; never on personal devices] |
7. Access control
[Access is granted on the principle of least privilege and requires approval from the information asset owner.]
[Every user has a unique account. Shared accounts are prohibited except approved service accounts held in the password vault.]
[Multi-factor authentication (MFA) is required for email, remote access, cloud services and all administrative access.]
[Privileged access is limited to named administrators, uses separate admin accounts and is reviewed monthly.]
[User access is reviewed quarterly by asset owners. Leavers’ access is removed by the end of their last working day; movers’ access is adjusted within 5 working days.]
[Passwords follow the Password Standard: minimum 14 characters or a passphrase, no reuse, managed through the company password manager.]
8. Acceptable use
[Company systems are for business use; limited personal use is allowed if it does not affect work or security.]
[Staff must lock screens when away, must not install unapproved software and must not disable security tools.]
[Confidential information must not be entered into unapproved external tools, including public AI services, unless approved by Information Security.]
[Full rules are in the Acceptable Use Policy, which all staff acknowledge at induction and annually.]
9. Cryptography
[Confidential and Restricted data is encrypted at rest (AES-256 or equivalent) and in transit (TLS 1.2 or higher).]
[All laptops and mobile devices use full-disk encryption.]
[Encryption keys are managed in the approved key management service with access restricted and logged.]
10. Physical and environmental security
[Offices use badge access; visitors sign in, wear badges and are escorted.]
[Server and network rooms are locked with access limited to IT staff and logged.]
[A clear-desk and clear-screen rule applies; confidential paper is shredded.]
[Equipment leaving the office is the user’s responsibility; loss or theft must be reported within 1 hour.]
11. Operations security
Control | Standard |
|---|---|
[Malware protection] | [Endpoint detection and response (EDR) on all endpoints and servers, centrally monitored] |
[Patching: critical vulnerabilities] | [Within 14 days of release (7 days if actively exploited)] |
[Patching: high vulnerabilities] | [Within 30 days] |
[Patching: other] | [Within 90 days or next maintenance cycle] |
[Backups] | [Daily backups of critical systems, one copy immutable or offline; restore tested quarterly] |
[Logging and monitoring] | [Security logs from key systems sent to central monitoring and kept for 12 months] |
[Vulnerability scanning] | [Monthly internal and external scans; annual independent penetration test] |
[Change management] | [Production changes approved, tested and recorded; emergency changes reviewed after the event] |
12. Network and communications security
[Networks are segmented: corporate, guest and production environments are separated by firewalls.]
[Remote access is through the approved secure access service with MFA.]
[Email is protected by filtering and domain authentication (SPF, DKIM, DMARC).]
[Confidential information is shared externally only through approved secure file-sharing tools.]
13. Supplier security
[Suppliers that access Confidential or Restricted information are risk-assessed before contract and reviewed annually.]
[Contracts include security and confidentiality obligations, breach notification, audit rights and, where applicable, data processing terms.]
[Supplier access is limited, time-bound and removed when no longer needed.]
14. Incident management
[All staff must report suspected security incidents or weaknesses immediately to the IT service desk or security@[company].com.]
[Incidents are handled under the Incident Response Procedure; personal data breaches follow the Data Breach Response Plan.]
[Significant incidents are reviewed to identify root causes and improvements.]
15. Business continuity
[Critical systems have documented recovery objectives (RTO and RPO) in the IT Disaster Recovery Plan, tested at least annually.]
[Information security requirements continue to apply during disruption.]
16. People security
[Background checks proportionate to the role are completed before employment, as permitted by local law.]
[Employment contracts include confidentiality obligations.]
[All staff complete security awareness training at induction and annually; phishing simulations run quarterly.]
[Return of assets and access removal are part of the leaver process.]
17. Secure development
[Software is developed following the Secure Development Standard, including peer code review, dependency scanning and secrets scanning.]
[Production data is not used in development or test environments unless anonymised or approved.]
[Security testing is completed before major releases.]
18. Compliance
[Tessaract complies with applicable laws, regulations and contracts, including [data protection law, e.g. GDPR], [sector regulations] and customer security requirements. Compliance with this policy is checked through internal audits, technical monitoring and an annual management review.]
19. Exceptions
[Exceptions must be requested in writing, risk-assessed by Information Security, approved by the policy owner and the relevant asset owner, recorded in the exceptions register and reviewed at least every 6 months.]
20. Enforcement
[Breaches of this policy may lead to disciplinary action up to and including dismissal, termination of contracts and, where applicable, legal action.]
21. Related policies and standards
[Acceptable Use Policy]
[Access Control and Password Standard]
[Data Classification and Handling Standard]
[Backup Standard]
[Incident Response Procedure and Data Breach Response Plan]
[IT Disaster Recovery Plan]
[Supplier Security Standard]
[Secure Development Standard]
22. Approval and acknowledgement
Role | Name | Signature | Date |
|---|---|---|---|
Chief Executive | [Name] | [Date] | |
Head of Information Security | [Name] | [Date] |
All staff must read and acknowledge this policy through the HR system within 14 days of starting and annually thereafter.