Secure delivery
Delivery practices, code review, testing, release controls and the security activities appropriate to the proposed system are agreed as part of the work.
Security, privacy, AI and procurement information for teams assessing Codefremics and a proposed engagement.
Controls depend on the system, data and scope. We describe boundaries rather than make blanket claims.
Controls depend on the service, deployment model, customer responsibilities and agreed scope. We describe those boundaries rather than make blanket claims.
Delivery practices, code review, testing, release controls and the security activities appropriate to the proposed system are agreed as part of the work.
Roles, permissions, privileged access, approval paths and customer responsibilities are reviewed against the system and operating model.
Data categories, handling requirements, hosting options, integrations, retention expectations and deployment responsibilities are made explicit before implementation.
Backup, recovery, monitoring, incident handling, support and escalation expectations are defined for the service being delivered.
Relevant third-party services and provider dependencies can be discussed in the engagement review, subject to the applicable commercial and confidentiality arrangements.
Bring the supplier, security, delivery or AI assurance questions your review team needs to resolve.
Start an assurance reviewWhen an engagement includes AI, we review the workflow, the data, the people responsible for decisions and what happens when the system is uncertain or wrong.
Identify the data involved, permitted processing, model or hosting options and relevant residency or cross-border requirements.
Set the review queue, named decision-maker and fallback route where a result affects customers, money, compliance or safety.
Agree how quality is tested, how performance is reviewed, how changes are approved and how incidents are handled.
Define the records needed for inputs, outputs, approvals and material changes, alongside relevant provider and subprocessor boundaries.
Public information is on this page. Sensitive architecture, security and supplier material is shared only through an agreed process.
Use the route that matches the question. Engagement-specific commitments are agreed in the applicable contract and supporting review materials.
Use the published security contact for responsible vulnerability reporting and related security enquiries.
Email security contact Read security.txtRead the public privacy statement or send a privacy enquiry to the listed privacy contact.
Email privacy contact Read the privacy statementNamed owners, review points, release control and handover are described in the delivery approach and the Responsible Delivery Policy.
See the delivery approach Read the delivery policyThis is public assurance information. It is not a certification, compliance or service-level statement. Engagement-specific commitments are agreed in the applicable contract and supporting review materials.
Bring the supplier, security, delivery or AI assurance questions your review team needs to resolve. We reply within 24 hours.
What to bring