How it works
A consistent route from first conversation to lasting improvement.
Managed clients and project clients follow different paths, but the habits are the same: understand first, preserve before changing, and document everything.
Onboarding a managed client.
Four steps, scaled to the size of the environment.
Assess
Inventory of users, devices, accounts, and systems, and a review of the risks that matter most.
Stabilize
Urgent issues fixed, backups verified, stale access removed, and admin credentials secured.
Secure
Baseline controls rolled out: multi-factor authentication, endpoint protection, and Microsoft 365 hardening.
Operate
Ongoing support, monitoring, and maintenance, with regular reporting and planning.
Running a project or investigation.
Five phases, scaled to the size of the problem.
- Understand
Establish the real question and the operational stakes. Every engagement starts with a direct conversation about what has actually happened, what decision depends on the answer, and what constraints exist. Scope, authorization, and access are agreed before any technical work begins.
- Preserve
Protect the evidence and the environment before acting. Where an investigation or incident is involved, relevant records are preserved before anything is changed. In operational work, current state and configuration are captured so changes are reversible and accountable.
- Analyze
Reconstruct the facts from correlated technical evidence. Audit logs, configuration, message traces, and system records are examined and correlated. Findings are grounded in what the evidence supports, with uncertainty stated plainly.
- Resolve
Take the actions the analysis actually justifies. Remediation, recovery, hardening, or configuration changes are carried out, or documented for your team, in priority order. Every recommendation is tied to a reason a decision-maker can follow.
- Strengthen
Leave the environment more defensible than it was found: improved logging, clearer controls, tested recovery, and documentation. The goal is durable improvement, not dependence.
Operating principles.
- Authorization and scope are agreed before technical work begins.
- Evidence and current state are preserved before anything changes.
- Findings are grounded in what the records support, and uncertainty is stated plainly.
- Every recommendation carries a reason a decision-maker can follow.
- Work closes by making the environment more defensible than it was found.
Ready when you are.
The first step is a direct discussion of your situation, to find out whether Syladon is the right fit.