Security
Practical security for governed delivery
Microcorem supports clients that need careful data handling, clear access boundaries and delivery they can explain to procurement and technical stakeholders. This page summarises our approach — not a certification claim or exhaustive control catalogue.
Security posture
Microcorem takes a proportionate, project-scoped approach to security for software, cloud, data and AI delivery work.
- Security expectations are agreed during scoping and procurement onboarding.
- Controls are matched to project sensitivity, data classification and delivery environment.
- We describe capability carefully and do not claim mature enterprise certifications we have not earned.
Data handling boundaries
We define what data is used, where it is processed, and how long it is retained before build work begins.
- Clear boundaries for client data, test data, logs and model inputs.
- Environment separation between development, staging and production where applicable.
- Documented handling expectations for integrations, exports and handover.
Access control
Access to systems, repositories and client environments is limited to what each delivery role requires.
- Least-privilege access for project contributors and specialist associates.
- Shared credentials avoided where individual access can be used instead.
- Access reviews aligned with project milestones and offboarding.
Delivery safeguards
Engineering delivery includes practical safeguards so work remains observable, reversible and accountable.
- Version control, change tracking and documented deployment steps.
- Monitoring and logging plans for pilots and production-bound work.
- Rollback and recovery considerations for critical workflows.
AI governance and human oversight
AI-assisted features are designed with human review points, especially where outputs affect operations, people or compliance.
- Clear limits on automated decision-making in sensitive contexts.
- Prompt, model and workflow documentation suitable for client review.
- Responsible-use considerations built into design, not added after delivery.
Incident response approach
If a security or data-handling concern arises during a project, we aim to respond quickly, contain impact and communicate clearly.
- Founder-led escalation for client-facing security matters.
- Containment, investigation and remediation steps agreed with the client.
- Post-incident review and practical improvements where warranted.
Procurement and security documentation
Security summaries, insurance information and supporting documentation can be provided on request during supplier onboarding, procurement review or contract due diligence.
Security questions: security@microcorem.io