01 · Understand & scope
Discuss the business trigger, systems, stakeholders and available evidence. Agree objectives, boundaries and deliverables.
Start with a defined business need. Agree a scope that fits the organization, available evidence and people who will carry the work forward.
Discuss the business trigger, systems, stakeholders and available evidence. Agree objectives, boundaries and deliverables.
Review the agreed evidence, identify gaps and dependencies, and agree practical priorities with management.
Provide the agreed outputs and support. Track actions and review progress at a cadence suited to the engagement.
A sponsor, relevant contacts, authorized evidence and time for review. Access and secure sharing are agreed before information is exchanged.
The outputs defined in the proposal: for example a risk register, evidence index, phased roadmap or management report.
Your executives and designated owners retain business decisions and risk acceptance. Recommendations, dependencies and unresolved questions are made explicit.
New systems, requirements or missing evidence may change effort and timing. Changes are discussed and agreed in writing.
A simple example shows the structure of a risk register and action roadmap. It is fictional and does not describe a client engagement.
View sample deliverable →Timing follows scope, available evidence and client review capacity. Working days and elapsed project time are agreed separately.
No. Certification decisions belong to an independent certification body. The engagement specifies the readiness support and evidence work included.
Implementation activities, access, specialist support and authorization are agreed explicitly. They are not assumed to be included in every advisory engagement.
Read the engagement principles
Discuss your priorities
A direct conversation with the founder
Founder · VLK InfoSec Consulting
Initial enquiries help establish the business need, the right scope and whether an engagement is a good fit.
About Milica →