Skip to content

Service 07 / Protect

Security, access & data governance

Build access controls and data handling into the system from the beginning, proportionate to the information and risks involved.

Rows of server racks and cabling inside the CERN Computer Centre
CERN Computer Centre · SwitzerlandSimonWaldherr · Credits ↗

The commission / an interactive walkthrough

See the work take shape.

Explore how this service moves from your starting information through a scoped build to testable acceptance and handover.

Your starting material

Gather the evidence.

We start with the users, records, constraints and decisions that the commission must respect.

  • 01Information categories and responsible owners
  • 02User roles, retention needs and known concerns
  • 03Existing controls and required specialist assurance

Share a representative example with private records removed; detailed access follows an agreed secure process.

Specific deliverables, assurance and acceptance depend on the agreed brief.

Explore our delivery process ↗

Make access and accountability part of the design.

01Authorise
02Record
03Review
Scope & deliverables

Where it fits

Applications & scope.

Staff systems, confidential records and services with different user permissions.

What we can deliver

  • 01Role-based permissions and access design
  • 02Audit trails and accountable user actions
  • 03Privacy-aware data collection and retention
  • 04Secure development review and remediation planning
Explore the system

System sketch / Illustrative permission boundary

Access follows responsibility.

Inside / Identify

Establish the user or service identity before deciding what information or actions it can access.

Identity
An authenticated user or service
Context
The relevant organisation or scope
Session
An agreed access lifecycle

Illustrative service architecture. Detailed rules and responsibilities are agreed for each commission.

The service journey starts before the application form ↗
Acceptance, QA & handover

A useful starting point

Bring the context.

  • Information categories and responsible owners
  • User roles, retention needs and known concerns
  • Existing controls and required specialist assurance

Acceptance & handover

Agree what good means.

  • Allowed and denied actions for each agreed role
  • Audit visibility and proportionate retention
  • Recorded findings, ownership and remediation priorities

HandoverAccess matrix, data-handling decisions and agreed security review findings.

From requirements to operation

A complete commission, not an isolated build.

01 / Gather & shape

Establish the foundations.

Information categories and responsible owners. User roles, retention needs and known concerns. Existing controls and required specialist assurance.

Strategy & discovery ↗
02 / Build & review

Make progress inspectable.

Implement the agreed scope in reviewable increments. Check user journeys, integration boundaries and failure conditions against the requirements, with unresolved decisions kept visible.

Review the delivery stages ↗
03 / Accept & hand over

Define what is ready.

Allowed and denied actions for each agreed role. Audit visibility and proportionate retention. Recorded findings, ownership and remediation priorities.

Access matrix, data-handling decisions and agreed security review findings.

Evidence and scope are different.

Working examples and archive captures show their stated maturity. The service scope is a commissioning capability, not a claim that every listed system has been deployed for a client.

Institutional delivery

Requirements first. Evidence throughout.

For public-sector and enterprise commissions, we agree the deployment approach, responsibilities, acceptance evidence and operational handover against the actual requirements.

Government & institutional capabilities ↗

Before commissioning

The questions worth asking.

Discuss your requirements ↗
How do you protect existing records during change?

We establish the authoritative sources, mapping rules and access boundaries first. Migration and integration scope includes reconciliation, error handling and recovery responsibilities; production writes and cutover require an agreed review.

Can you work with our existing systems?

Yes, where access and integration are authorised. We first establish ownership, documentation, dependencies and the boundaries of any replacement or connection. A commission does not require abandoning a system that already works.

How do we agree the first release?

We prioritise complete user tasks rather than an arbitrary feature count. Scope, exclusions, dependencies and acceptance scenarios are agreed before implementation, with review points for changes.

How are security and personal data handled?

We identify data owners, information categories and permitted actions during discovery. Controls, retention, specialist assurance and any data-processing responsibilities are scoped against the actual service. A studio credential does not certify your future system.

What happens after handover?

Documentation, access ownership, training and operating responsibilities are agreed before release. Maintenance, incident coverage and further development have an explicit scope; they are not assumed to be unlimited.

The standard behind the work

Designed to be used.
Built to be owned.

Delivery & acceptance ↗
01

A clear decision trail

Scope, assumptions, dependencies and changes recorded against the brief.

02

Evidence before acceptance

User journeys, permissions, failure conditions and operating requirements reviewed before release.

03

Ownership beyond launch

Source, documentation, training and recovery responsibilities agreed as part of handover.

Credentials & project assurance ↗

Start a conversation

Tell us what needs to work.

Bring the brief, the source material and the constraints. We will help define the scope and the right next step.