Information security policy and program
October 1, 2026
Purpose and scope
This program defines how Modern Training Solutions, LLC protects information used to deliver Learning Cub services. Its goals are to keep information accessible only to authorized people, accurate and protected against unauthorized changes, and available when needed.
It applies to employees, contractors, and company-managed systems supporting Learning Cub, including its website, learning platforms, business accounts, software, devices, and customer information. For customer-managed or vendor-managed systems, responsibilities must be agreed with the relevant party. Outsourcing a service does not remove our responsibility to assess how our information is protected.
Responsibilities
Management approves the program, appoints a security coordinator, provides reasonable resources, and decides whether significant unresolved risks are acceptable. The coordinator may be an existing staff member; a separate security department is not required.
The security coordinator maintains the program, coordinates risk reviews and incident handling, and tracks improvements. Technical staff manage access, updates, backups, and security settings for systems under their control. All employees and contractors must protect company and customer information, follow applicable procedures, and promptly report suspected problems to the coordinator or management.
One person may hold multiple roles except where this program requires separation of approval and execution. Assigned names and internal contact details are maintained in an internal record available to staff. Management approval of this program and its supporting procedures must be recorded before they take effect. Requirements below are the proposed operating baseline; incomplete controls remain recorded gaps until implemented and verified.
Identify systems and assess risks
The coordinator maintains one centralized asset inventory covering hardware, software, information assets, and physical assets used to deliver services. Record each asset’s identifier, owner, location or hosting provider, purpose, information classification, and relevant dependencies. A restricted spreadsheet or linked register with one authoritative index is sufficient. Update it when assets are added, materially changed, reassigned, or retired, and review it at least annually. Information is treated as public, internal, or confidential. Personal information, credentials, and nonpublic customer records are confidential.
At least annually, and before significant changes, the coordinator reviews likely risks such as stolen accounts, accidental disclosure, software vulnerabilities, service outages, and data loss. Each material risk is recorded with its likely impact, priority, responsible person, and planned action or management-approved acceptance.
A spreadsheet or issue tracker is sufficient. Higher-impact and actively exploited risks receive priority. Applicable customer commitments and legal requirements are considered when choosing safeguards.
Basic safeguards
The following requirements apply to systems and information within our control:
- Access: Give every employee and contractor a unique, individually attributable identity and require authentication before access to organizational systems and networks. Give each person only the access needed for their work, approve access before provisioning, and remove it promptly when no longer needed. Review access to important systems at least annually and when responsibilities change. Systems unable to support attributable access require a documented gap and remediation plan.
- Privileged accounts: Administrative and other elevated access must be approved by management or the security coordinator and limited to people who need it for their duties. Use individually assigned accounts and use standard access for routine work where practical. The security coordinator or designated technical person reviews privileged accounts at least annually and when staff leave or responsibilities change, including employee, contractor, and service accounts. Remove or reduce unnecessary privileges promptly. Record the review date, reviewer, accounts checked, and any resulting actions in a ticket or spreadsheet.
- Account protection: Use strong, unique passwords and a password manager. Require multi-factor authentication for administrative accounts, business email, and all remote connectivity to organizational systems, including VPN, remote desktop, remote server administration, and remote access to customer information. Unsupported access routes must be blocked or protected through an MFA-enforcing gateway before use; record any unmet requirement as a gap.
- Devices: Protect work laptops, phones, tablets, and other mobile devices with screen locks, supported software, security updates, and appropriate malware protection. Enable full-disk or device encryption using a supported implementation of AES-128, AES-256, or an equivalent strong industry-standard algorithm on devices that store or access organizational or sensitive information. Use encrypted connections when accessing organizational services. Store recovery keys securely with access restricted to authorized people, separately from the device. Verify encryption before granting access and at least annually afterward, recording the check in the device inventory. Devices that cannot meet these requirements must not store or access organizational or sensitive information.
- Data handling: Collect and retain only information needed for business, contractual, or legal purposes. Use approved services, encrypted connections for confidential data transfers, and encryption for stored confidential information where supported. Restrict access to exports and backups. Securely delete or anonymize information when it is no longer needed, accounting for backup retention and required records. Follow the Media and device disposal and reuse procedure before reassignment, return, or disposal.
- Software and changes: Track relevant security updates and prioritize fixes according to risk. Review and test material changes before release, keep source changes in version control, and maintain a practical rollback approach. Keep passwords and other secrets out of source code and public documents. Follow the management-approved Secure development and change control policy for development, configuration changes, and releases.
- Security updates and patches: Technical staff check for available security updates at least monthly and apply applicable patches and fixes to all organization-managed servers and applications on a monthly cycle, with no applicable security update deferred beyond one calendar quarter without a documented, management-approved exception and temporary safeguards. Critical or actively exploited vulnerabilities receive priority for earlier remediation. Check that affected services work after updates and record completion in a ticket or maintenance log. For provider-managed systems, confirm the provider’s responsibility for patching.
- Third-party risk assessment: Before engaging subcontractors, affiliates, suppliers, or other third parties used to deliver customer services, the security coordinator or management assesses risks proportionate to the third party’s access to information and importance to service delivery. Consider the information they handle, their security and privacy safeguards, service reliability, and relevant customer requirements. Review available security documentation or request clarification where needed. Record the assessment, identified concerns, and approval in a ticket or spreadsheet. Address significant risks before engagement or document management’s acceptance with appropriate safeguards. Reassess important third parties at least annually and after significant service changes or security incidents.
Control gaps must be recorded and addressed through planned actions or approved exceptions; they must not be silently treated as implemented.
Identity, credentials, and managed devices
Shared accounts: Generic or shared interactive accounts must not be used for routine access to systems containing sensitive data. Non-interactive service accounts must have a named owner, a documented purpose, restricted permissions, and protected credentials. Individually authenticated access to shared mailboxes is permitted; sharing a mailbox password is not. If an emergency account is unavoidable, restrict and log its use, identify the individual using it, review each use, and rotate its credentials afterward. Record and disclose any such exception when answering questions about shared accounts.
Separate access approval and provisioning: A manager or designated system owner authorizes access, and a different authorized person provisions it. No person may approve their own access. Record the requester, approver, provisioner, permissions, and completion date in a ticket. If staff availability prevents separation, record the gap and a management-approved compensating review; this does not establish full segregation of duties.
Passwords: Require unique passwords or passphrases of at least 15 characters for staff accounts, preferably generated and stored by an approved password manager. On systems we control, allow at least 64 characters, spaces, password-manager autofill and paste; block common and compromised passwords and rate-limit failed authentication attempts. Do not impose arbitrary character-composition rules or routine expiry without evidence of compromise. Change passwords promptly after suspected compromise or unauthorized disclosure. Where a provider cannot enforce these controls, require staff to follow the length and uniqueness rules and document the technical limitation and alternative protections.
Credential protection: Protect authentication credentials in transit using TLS 1.2 or later or another appropriate encrypted protocol such as SSH. Store password verifiers using a supported salted, computationally expensive one-way password-hashing function, not plaintext or reversible password encryption. Encrypt recoverable secrets such as API keys, tokens, and private keys at rest using an approved secret store, and restrict and audit access. Protect credential backups and recovery material similarly; exclude secrets from source code, logs, tickets, and unprotected messages. Review vendor authentication documentation where the provider controls storage.
Corporate mobile devices and MDM: Only company-owned laptops, phones, tablets, and other mobile endpoints enrolled in mobile device management (MDM) may access customer data. Enforce encryption, screen lock, supported software, update compliance, and remote lock or wipe through management controls, and block unmanaged or noncompliant access through device-aware access controls. Personal devices must not access customer data. Existing personal-device access remains a recorded implementation gap until company equipment and enforcement are in place; the disposal procedure still applies to removal of any previously stored company data.
Physical protection and customer separation
Physical access: Limit access to buildings and areas where customer data is stored, transmitted, or processed to authorized personnel based on their duties. Maintain and review authorized access, promptly revoke obsolete access, and supervise visitors. Remote workers must prevent household members and visitors from accessing work devices or records and securely store them when unattended. For hosted infrastructure, retain evidence of the provider’s physical access controls and responsibility for the facilities.
Customer separation: Separate different clients’ data and processing activities using physical separation, network segmentation, or isolated virtual machines or containers with enforced access and network boundaries. Document and test those boundaries before onboarding a client and after material changes. Restrict databases, file storage, exports, backups, and administrative access to the appropriate client boundary, with any cross-client administration explicitly authorized and logged. Application roles or groups within a shared Moodle installation alone do not satisfy this infrastructure-separation requirement. Where clients share such an installation, record the gap and obtain the customer’s explicit acceptance of logical separation or implement a qualifying boundary before claiming this control is met.
Preventive protection and vulnerability management
Web application firewall: Protect internet-facing applications handling customer information with a configured web application firewall (WAF). Route application traffic through it, restrict direct-origin bypass, enable relevant attack protections, review alerts, and test coverage after material changes. Record provider-managed coverage where applicable; a general network firewall alone is not a WAF.
Email and browsing protection: Scan all incoming email attachments for viruses and malicious code before user delivery. Quarantine attachments that cannot be safely scanned rather than silently passing them through. Automatically mark emails from external senders in the subject or body. Apply filtering or blocking to internet-facing email and staff web browsing to reduce phishing, malware, and access to known malicious destinations. Enable the controls through approved email and endpoint, DNS, or web-security services and retain configuration evidence.
Endpoint detection and response: Deploy and maintain an endpoint detection and response (EDR) solution on company endpoints and servers that support customer services or access sensitive information. Monitor agent health, forward detections to the response process, and investigate threats. Record unsupported systems as gaps with alternative protection and a remediation plan; basic antivirus alone must not be described as EDR.
Vulnerability scanning: Perform authorized vulnerability scans at least quarterly and after significant changes on internal and externally facing systems supporting customer services or processing customer information. Include operating systems, applications, and relevant network services, using authenticated scans where supported. Track scope and inaccessible assets, results, owners, remediation dates, and verification. Obtain authorization before scanning third-party infrastructure and review appropriate provider evidence for provider-controlled layers.
Penetration testing: Arrange authorized penetration testing at least annually and after changes that materially affect security boundaries, covering internal and externally facing systems supporting customers or processing customer information. Use qualified personnel sufficiently independent of the implementation being tested, agree scope and safe testing conditions, retain the report, and verify remediation. Automated vulnerability scanning alone does not replace penetration testing; provider reports cover only their stated scope.
Remediation: Record security findings with severity, affected assets, owner, due date, and corrective action. Assess critical or actively exploited findings immediately and apply containment as soon as practicable. Target remediation within 7 days for critical findings and 30 days for high-risk findings, sooner where exposure or customer commitments require it. The clock starts when the finding is identified. Verify fixes by rescanning or retesting. If a target cannot be met, management must approve temporary safeguards, a revised date, and the remaining risk before the target expires. Track overdue issues and notify affected customers when required; exceptions do not mean the original target was met.
Detect and report problems
Technical staff enable useful security logs and available alerts for important systems, proportionate to risk. These may include unusual sign-ins, administrative changes, and backup failures. The coordinator records who receives alerts, how often logs need review, and any monitoring gaps. Logs must be protected against unauthorized access and retained for a documented period appropriate to operational and contractual needs.
Staff must promptly report suspected phishing, lost devices, exposed information, unauthorized access, or unusual system behavior to the coordinator or management. They should report concerns even if they are unsure an incident has occurred.
Security alerts must be configured for suspicious activity in organization-managed applications, platforms, and network devices, using available monitoring features or a centralized monitoring service. Technical staff select relevant events, such as repeated failed sign-ins, unexpected privileged-account changes, or suspicious network activity, and route notifications to a designated person for investigation. Check alert delivery when configured and at least annually. Record coverage, recipients, and any gaps in a ticket or monitoring inventory. For provider-managed infrastructure, confirm the provider’s monitoring responsibilities and how relevant incidents are reported to us.
Continuous monitoring: Maintain security-event collection, detection, and alerting 24 hours a day, seven days a week for systems supporting customer services, with a documented on-call rota and backup or a contracted monitoring service able to review and escalate alerts at any time. Define alert severity, response expectations, and escalation contacts; test routing and review monitoring health. Office-hours-only review or an unattended email inbox does not satisfy this requirement.
Respond and recover
The security coordinator coordinates response to suspected incidents affecting customer assets or information, company systems, or service delivery. Management appoints a backup contact when the coordinator is unavailable. Keep internal escalation contacts and customer notification contacts in a restricted location accessible during an outage.
Management designates an incident response team with a response lead, technical investigator, communications owner, and backups. Existing staff may hold these dedicated response responsibilities alongside normal duties, supported by a retained external specialist where needed. Record names, contact details, availability, and escalation arrangements, and activate the team to investigate, analyze, and respond to confirmed incidents. Confirm with the requesting customer whether it requires a separate full-time team.
For a suspected incident, the coordinator works with technical staff and management to:
- Monitor and report: Use the monitoring and reporting arrangements in the “Detect and report problems” section to identify potential incidents. Employees and contractors must promptly report concerns to the coordinator or management without waiting for confirmation.
- Assess and escalate: Record when the concern was reported, what happened, and which customers, assets, systems, or information may be affected. Assess urgency based on potential exposure, disruption, and ongoing harm. Escalate serious or ongoing incidents to management immediately.
- Contain and preserve evidence: Limit harm, such as by disabling affected accounts or isolating devices. Preserve relevant logs, messages, and other evidence, restrict access to them, and record actions taken. Avoid unnecessarily altering evidence during investigation.
- Investigate: Assign technical staff or an appropriate service provider to determine the cause, scope, timeline, and whether customer assets or information were accessed, changed, lost, or disclosed. Document findings and remaining uncertainty.
- Notify: Management coordinates notification to affected customers without undue delay when an incident affects their assets or information, or when otherwise required by an applicable agreement or law. Follow specified notification deadlines and do not wait for the full investigation if earlier notice is required. Use agreed customer contacts and secure communication channels. Include known facts, likely impact, actions taken, recommended customer actions, and a follow-up contact. Agree a regular update schedule with the affected customer, provide at least daily status updates while a material incident remains active unless a different schedule is agreed, and communicate significant developments sooner. Provide investigation results and corrective actions at closure, identifying any unresolved uncertainty and protecting other customers’ information. Determine whether affected individuals, providers, or authorities also require notification, and record when, how, and to whom notices were sent.
- Recover and improve: Correct the cause, restore services from a known safe state, and check for continuing compromise. Record the outcome, lessons learned, and follow-up actions with responsible owners.
Keep incident records in a restricted ticket or document. Review these response and notification arrangements at least annually and after significant incidents. A brief walkthrough of an example incident is sufficient to check responsibilities, contacts, and response steps.
Backups and disaster recovery
Backup procedures: Technical staff maintain documented backup procedures for systems, applications, configuration, and customer and business data, approved by management. For Moodle, include the database, uploaded file storage (moodledata), application and plugin versions, and necessary configuration and securely held recovery secrets; a database backup alone is insufficient. Specify scope, frequency, retention, encryption, access, isolated or immutable/offline copies, and acceptable data loss. Record backup success or failure, check each scheduled run through automated reporting or a documented review, and promptly investigate failed or missed backups.
Disaster recovery program: Management approves a documented disaster recovery program and technical recovery plan, including service priorities, recovery time and recovery point objectives, restoration order, dependencies, clean recovery environments, provider escalation, assigned owners and backups, and return-to-service validation. Record approval and communicate relevant responsibilities and arrangements to staff, contractors, affected customers, and providers. Keep the plan and necessary recovery access available during an outage, protect sensitive details, and review at least annually and after major changes.
Restore testing: Test backup and restoration procedures at least annually and after major recovery changes, using an isolated environment and representative systems, applications, and data. Verify restored data integrity, application operation, required dependencies, and achieved recovery time and data loss against the plan. Record test scope, results, and every issue; assign owners and due dates, remediate findings, and retest affected steps to confirm resolution. Track any untested recovery paths and schedule them. A backup-success message alone is not a restoration test.
Business continuity
Management approves and supports a business continuity program to maintain or restore essential services during disruptions, including system outages, cyber incidents, loss of a key provider, or staff unavailability.
The security coordinator maintains a practical internal continuity plan with input from management and technical staff. The plan identifies:
- Essential services, their dependencies, and recovery priorities.
- Acceptable downtime and data loss, taking customer commitments into account.
- Responsible staff, backup contacts, and key service-provider contacts.
- Recovery steps and temporary working arrangements, including alternatives when key systems, providers, or personnel are unavailable.
- How employees, contractors, affected customers, and relevant providers will receive updates during a disruption.
Management approves the plan and significant changes, with approval recorded in a ticket, email, or meeting note. Communicate relevant responsibilities and arrangements to employees, contractors, and other interested parties, including customers and providers where applicable. Share only the information each party needs and keep sensitive operational details restricted.
During a disruption, management or its designated backup activates the plan, coordinates recovery, and ensures affected parties receive appropriate updates. Use the incident-response and backup arrangements in this program where relevant.
Review the plan at least annually and after significant disruptions or changes. Conduct a brief walkthrough or practical exercise at least annually, record the results, and assign any necessary improvements.
Staff guidance
Employees and contractors must complete security awareness training when they join and at least annually. Cover account protection, phishing, safe information handling, device security, approved AI use, and incident reporting. A brief course, briefing, or written training with recorded completion is sufficient; track participants, dates, content or version, and overdue follow-up.
Employees and contract workers must read and acknowledge applicable security and compliance policies and procedures when joining, at least annually, and after material changes. Retain individual acknowledgment dates and policy versions, and follow up on missing acknowledgments.
Personnel screening: Before granting sensitive-data access to employees, contractors, or third-party service personnel, management arranges screening appropriate to the role and applicable law, including verification of employment history, criminal-record checks, prohibited-party checks, and drug screening where lawful and permitted for that role. Obtain required notices and consents, restrict screening records, and use a qualified provider where appropriate. For supplier personnel, obtain contractual assurance and evidence of equivalent checks. Document any legally restricted, unavailable, or omitted check and disclose the limitation in questionnaires; do not claim that all listed checks were performed when they were not.
Supplier obligations
Require third-party service providers to adhere to applicable organizational security policies and standards when providing customer services. Identify the relevant requirements before engagement and include them, or explicitly mapped equivalent obligations, in a contract or other binding agreement. Cover confidentiality, access, incident notification, data handling, subcontractor obligations, and return or deletion of information as relevant. Retain the agreement and review compliance through proportionate evidence or follow-up. If a standard vendor agreement does not meet a required obligation, record the gap and resolve it or disclose it to the customer rather than assuming compliance.
AI use and risk management
Current use and register: The organization currently uses AI tools to support its work. The security coordinator maintains a simple register of current and planned AI uses for the next 12 months, including coding, content tools, supplier features, and any customer-facing capabilities. Record the owner, purpose, provider, information involved, approval, and status. Existing uses must also be reviewed; staff use does not imply that AI is embedded in customer-facing products.
Approved tools and provider settings: Use only AI tools and integrations approved by management or the security coordinator. Before approval, review the provider’s security, data retention and deletion, access controls, and use of submitted information for model training. For nonpublic company information, require suitable contractual protections and settings that prevent its use for provider model training. Use approved work accounts, restrict shared links, and apply the program’s authentication requirements.
Protect information: Submit only the minimum information needed. Prefer public, synthetic, or irreversibly anonymized data. Do not enter passwords, API keys, authentication tokens, private keys, or other live secrets into prompts or attachments. Customer confidential information, personal data, and nonpublic source code require specific authorization from the responsible information owner and the security coordinator, suitable provider protections, and any required customer permission before submission. Check files, screenshots, logs, and repository context for hidden or unintended sensitive content before uploading or enabling automatic access.
Human review and safe actions: Treat AI outputs and instructions found in uploaded documents, websites, or retrieved content as untrusted. Verify important facts and references, check for inappropriate disclosure or bias, and review relevant ownership or licensing restrictions before use. Review and test AI-generated code under the secure development and change-control policy. Give AI integrations only the permissions and data they need. Require an authorized person’s approval before external messages, production changes, deletion, or other consequential actions; AI must not bypass existing access or approval controls. Do not rely solely on AI for decisions materially affecting customers or individuals.
Assess and manage risks: Before approving a use or material change, map its purpose, data flows, affected people, and dependencies; measure risks with proportionate checks of accuracy, privacy, security, harmful bias, and foreseeable misuse; and manage those risks with access limits, human review, monitoring, and a stop or fallback process. Record findings, acceptance criteria, results, approval, and follow-up actions in a ticket or register. A brief review is sufficient for low-risk uses. Review approved uses at least annually and after significant changes or incidents.
Retention and incidents: Protect saved prompts, outputs, and AI activity records according to their information classification. Retain them only as needed under applicable retention requirements, and use provider deletion controls when appropriate. Promptly report unintended disclosure, suspicious instructions, unauthorized AI actions, or harmful output through the incident-response process. Suspend affected access when needed, revoke exposed credentials, and investigate before resuming use.
Staff guidance: Include these AI rules in onboarding and annual security training, with practical examples of safe data sharing, checking generated output, and reporting concerns.
Review, exceptions, and records
At least annually, the coordinator reviews this program with management, including significant risks, incidents, access reviews, recovery checks, and overdue actions. Update it when services, risks, or obligations change materially.
If a requirement cannot reasonably be met, management must approve a documented exception stating the reason, risk, alternative safeguards, responsible person, and review or expiry date. Exceptions cannot override applicable legal or contractual obligations. An approved exception does not by itself justify answering Yes to a requirement that is not met. Keep implementation status and supporting evidence separate from policy wording.
Maintain lightweight internal records of program approval, role assignments, system and risk lists, agreed operating schedules, staff guidance, key checks, incidents, and exceptions. Existing tickets, meeting notes, or spreadsheets may serve as evidence; a dedicated compliance platform is not required. Restrict sensitive operational details to authorized people.
This program is the foundation for supporting security policies and procedures. It does not by itself establish certification or compliance with a particular security standard.
Supporting guidance
Password requirements draw on NIST SP 800-63B-4. The 15-character minimum for all staff passwords is our proposed baseline. Scanning frequencies, remediation targets, and notification cadence in this draft are proposed organizational choices, not claims that NIST mandates those exact schedules.