Scope before start
Every engagement starts with the environment, the problem, the expected outcome and constraints (time, access, law, budget). I reply with a proposed scope; only then come terms and invoicing. I do not sell “a full SOC on subscription” or a guarantee of recovering money after fraud.
Boundaries
- Work only within an agreed scope and on systems you own or are clearly authorised to involve.
- No testing of third-party networks, accounts or apps “just in case”, and no bypassing third-party controls.
- No promise to evict an attacker in fifteen minutes and no round-the-clock SOC roster — unless scope and terms say so explicitly.
- Digital forensics and IR: order and evidence preservation beat “wipe it so it works again”.
- A pentest, ISO conformity assessment or CERT-style audit only if the scope names that service explicitly.
Format and billing
Remote or on-site — after we agree. Phone: phone temporarily unavailable. Form replies usually within 1 business day; work timing is agreed individually. Polish VAT PL 6492193863. For remote billing I work with partner company Xolo Go OÜ, VAT EE102156920.
Engagement material
Do not paste logs, disk images or case notes into the form “just in case”. We agree the channel and scope first. Retention rules: Privacy.
Related
- Where to start — quote, consultation, engagement
- FAQ
- Vulnerability disclosure for tomek.st
- Services