
Built for consequence.
Cerebro Dynamics systems are designed for places where mistakes cost lives, capital, or sovereignty. Security is not a module. It is the architecture we build everything else upon.
Six tenets.
- 01Sovereign by default
Where the data lives, who can see it, how it leaves - these are mission decisions, not vendor decisions.
- 02Classification-aware
Access controls, redaction, and release aligned to national baselines and partner agreements.
- 03Auditable by construction
Every action is timestamped, signed, and reviewable. Audit is not a feature - it is the substrate.
- 04Resilient under stress
Operational integrity in degraded, contested, and disconnected environments.
- 05Zero-trust architecture
No implicit trust. Identity, device, network, and workload are continuously verified.
- 06Supply-chain integrity
Reproducible builds, signed artifacts, attested deployments, controlled change.
Live audit.
Frameworks we operate under.
Security & compliance notice.
Six design tenets. These are the principles we design to and hold ourselves to. They describe our engineering approach, not a certification. 01 Sovereign by default: where data lives, who can see it and how it leaves are decisions for the customer, and our architecture lets customers make and enforce them. 02 Classification-aware: access control, redaction and release are designed to align with national baselines and partner agreements. 03 Auditable by construction: actions are designed to be timestamped, signed and reviewable. 04 Resilient under stress: we design for integrity in degraded, contested and disconnected environments. 05 Zero-trust architecture: no implicit trust, with identity, device, network and workload verified continuously. 06 Supply-chain integrity: reproducible builds, signed artifacts, attested deployments and controlled change.
Compliance status. We state the status of each framework plainly so you can rely on it. Our security programme is built to align with ISO/IEC 27001, SOC 2, NIST SP 800-53, the EU and UK GDPR and the Kenya Data Protection Act, 2019. Alignment means we are building our controls against these frameworks. It is not a certification, attestation or authorisation unless the status table below says so. FedRAMP, DoD Impact Level and STIG references describe control baselines we use as design inputs. We hold no US federal authorisation. HIPAA is a US law that does not directly apply to us as a Kenyan company; our health-data controls are designed with comparable safeguards and in line with the Kenya Data Protection Act and applicable health-sector rules. [INSERT STATUS TABLE: Framework | Status (Certified / Audit in progress / Aligned-to / Planned) | Scope | Date | Auditor. List a framework as Certified only when you hold the certificate or report.]
Illustrative displays. Any console, log, audit or dashboard shown on this website is a simulated illustration. It does not show real customer data, real operations or real partner activity, and any organisation names it contains are examples only.
Data protection. We process personal data under the Kenya Data Protection Act, 2019 and its Regulations. We are registered with the Office of the Data Protection Commissioner as [CONTROLLER AND PROCESSOR] under number [ODPC NUMBER]. Where we process personal data for a customer, we do so as a processor, on documented instructions, under a written agreement. We apply data protection by design and by default, and we carry out data protection impact assessments where processing is likely to result in high risk.
Data location. Customer data is hosted where the customer decides. Where the law requires data to stay in Kenya, including processing in categories the Data Protection Regulations treat as strategic interests of the State and data on critical information infrastructure, we deploy on servers located in Kenya and provide the documentation needed for regulatory approval. Cross-border transfers follow the Act, the General Regulations and the ODPC's guidance. We do not use customer data to train AI models or for any purpose other than delivering the agreed service.
Incident response and notification. We maintain an incident response plan. Where we act as a processor, we notify the customer without delay and, where reasonably practicable, within 48 hours of becoming aware of a personal data breach, so the customer can meet its own 72-hour duty to the ODPC. Where a customer system is designated critical information infrastructure, we support the customer in meeting its 24-hour incident-reporting duty. We tell customers promptly of any security incident that affects their data or service.
Deployment models. Our platforms are designed to deploy in sovereign on-premise, air-gapped, national-cloud and hybrid or edge environments, according to each customer's mission and legal requirements.
Secure development and supply chain. Our policy is to peer-review code changes, scan dependencies and secrets, sign build artifacts, separate environments, restrict production access to least privilege, and have an independent party test our software for vulnerabilities before customer go-live and on a regular cycle. We assess third-party providers before use and bind them by written security and confidentiality terms.
Responsible AI. Where our platforms use artificial intelligence, we design for human review at consequential decision points, with model use logged and outputs attributable. See our Responsible AI page.
Vulnerability disclosure. We welcome reports from security researchers acting in good faith. See our Vulnerability Disclosure Policy, or write to [email protected].
Limits. No system is perfectly secure, and we do not guarantee that our systems will be free from vulnerabilities or interruption. Specific security commitments, service levels and liabilities are set out in the written agreement with each customer, and those terms prevail over this page. Last reviewed: [DATE].
Contact. Security questions and briefings: [email protected]. Privacy matters: [email protected].