Define ISMS boundaries
Clarify services, teams, assets, dependencies and what belongs inside the ISMS scope.
POSSIBLE OUTPUT → Draft scope and stakeholder map
[ EXPERTISE / ISO / IEC 27001 ]
MAKE SECURITY MANAGEABLE.
BUILD A WORKING ISMS.
I help translate ISO/IEC 27001 requirements into a risk-based information security management system that teams can actually maintain.
[ MISSION BRIEF ]
PRACTICAL SUPPORT.
CLEAR PRIORITIES.
An ISMS should support decisions and accountability, not create paperwork for its own sake. My approach starts with scope, interested parties, risk and existing operating practices.
I can help structure a pragmatic implementation plan, clarify ownership and build useful evidence and review routines. Certification decisions and independent audits remain with accredited bodies.
[ OPERATION MODULES ]
FROM ANALYSIS
TO ACTIONABLE OUTPUTS.
Risk assessment and treatment
Create repeatable criteria and connect prioritised risks to owners and treatment options.
POSSIBLE OUTPUT → Risk methodology and treatment backlog
Control implementation planning
Map relevant controls, evidence sources and responsibilities without overengineering.
POSSIBLE OUTPUT → Control register and SoA working draft
Operational ISMS rhythm
Establish reviews, metrics, corrective action and internal audit preparation.
POSSIBLE OUTPUT → ISMS operating calendar
[ ENGAGEMENT PROTOCOL ]
HOW WE CAN WORK TOGETHER.
01 / DISCOVER
Clarify objectives, systems, stakeholders, existing evidence and constraints.
02 / PRIORITISE
Focus on risks, decisions and improvements that matter most.
03 / IMPLEMENT & REVIEW
Agree clear deliverables, ownership and a sensible way to review progress.
[ START A CONVERSATION ]
READY TO MOVE FORWARD?
LET'S DEFINE THE NEXT STEP.
Tell me about your situation and what you would like to improve. We can discuss a practical starting point.
GET IN TOUCH ↗