Approach
Technical decisions. Clear responsibilities.
The project begins with your needs and the consequences of a failure or compromise. Tools come later, once we know what they need to achieve.
From need to outcome.
A direct engagement can include architecture, implementation and verification. Ongoing management is included when it provides practical value and fits the agreed scope.
- 01
Understand the context
We map information, systems and dependencies, and establish what needs protecting, from which events and within which constraints.
- 02
Define the architecture
We turn those needs into requirements, boundaries and procedures. Alternatives are considered for cost, complexity and the ability to change suppliers.
- 03
Implement the decisions
We deliver the agreed changes and document configurations, access and responsibilities. The result needs to remain understandable and manageable.
- 04
Verify and hand over
Agreed tests check the results. The handover distinguishes what was observed, what remains unverified and any follow-up work.
Two ways to engage
Cerberox can take a direct engagement from architecture through verification. Alternatively, it can implement a Blueprint prepared by Gianfabio Chianura, who also works personally as a Data Security Architect.
A client who commissions the Data Security Architect remains free to choose another implementation provider. When Cerberox checks its own implementation, that check is not described as independent third-party assurance.
The next step
Let’s start with the actual problem.
Tell us what needs protecting and what the consequences of failure would be. We can then define a clear scope, responsibilities and next steps.