Security governance
Maturity assessment, security policies, data classification and supplier requirements.
Proposed deliverables: Maturity report, frameworks and a prioritised roadmap.
Protect systems. Strengthen cyber defence.
Governance, audits, cloud security and AI for analysts: modular support with human oversight and skills transfer.
Offer architecture · Scope to be definedA useful scope. An explicit architecture.
- Security governance and frameworks
- Audits and authorised penetration testing
- Cloud and migration security
- AI for cyber defence and secure AI use
- Training and skills transfer
Work begins with an analysis of available data, responsibilities, regulatory constraints and acceptance criteria. These capabilities do not constitute a reference to an already deployed implementation.
Five modules. Your priorities first.
Independent modules selected according to team maturity and the risks to address. Scope, resources and commitments are defined at the outset.
Audits and penetration testing
Assessment of priority services within an explicitly authorised scope and agreed rules of engagement.
Proposed deliverables: Ranked vulnerabilities, remediation plan and retesting.
Cloud security
Architecture review, hardening and secure migration to the selected infrastructure.
Proposed deliverables: Secure architecture documentation and hardening guides.
AI for cyber defence
Alert triage support, anomaly detection and assistance for analysts. Arabic and French capabilities are evaluated in their usage context.
Proposed deliverables: A prototype evaluated with the teams and preparation of SOC / CSIRT capabilities.
Training and awareness
Staff and analyst training, authorised simulated phishing exercises and transfer of tools and methods.
Proposed deliverables: Training programme and progress indicators.
Secure AI. Transfer control.
The offer also covers AI use: usage policies, data protection, model selection and human oversight. AI supports analysts; it does not replace their validation.
Data residency, flows and dependencies are documented with your teams. Sovereign hosting and open model options are assessed before sensitive data is processed.
Each engagement includes documentation, training and handover of tools to the teams. The first step is to agree a maturity assessment, identify priority systems and build a roadmap.
Scope. Build. Verify. Transfer.
A structured progression adapted to context. Commitments are defined with your teams; no deployment timeline is presumed.
Scope
Use cases, data, risks and acceptance criteria. Define what must remain under control.
Build
An explicit architecture and an initial scope your teams can evaluate.
Verify
Test relevance, access, limitations and operating conditions.
Transfer
Document, train and prepare for supervision and system evolution.
Clear answers. Precise commitments.
Does KEMITYA offer already deployed solutions?
The three domains are offer architectures. No client or government deployment is claimed here. Commitments are defined within a documented scope.
What does “sovereign” mean in this approach?
Sovereignty means the ability to control data, jurisdiction, access, dependencies, portability and governance. These principles only become guarantees once the chosen architecture has been verified.
What is the relationship with STIPway?
The founding brief describes expertise cultivated through STIPway. KEMITYA has an independent identity. The exact legal and commercial relationship remains subject to founder validation.
Is the Mauritania prototype an official service?
No. It is an experimental exploration requiring an audit, illustrated here by a local simulation using only fictional data. No contract or approval is claimed.
Your context. Our starting point.
Describe the use case, the constraints and the teams involved. A useful conversation begins with a clear scope.