How we work
Plan, test, check, hand over.
The procedure is ordinary. The important details are who is acting, what may change and which final check will settle the result.
- 01
Scope
Write the test and its limits before opening a tool.
The rules of engagement name the systems, accounts, target state, permitted actions, test window, contacts, evidence handling and stop conditions. Assumptions are listed separately so they can be checked.
- 02
Baseline
Show the expected result before changing anything.
A known-good or expected-denial case tells us that the fixture and observation path work. We record actor, object, marker and clock source before the main test.
- 03
Exercise
Run the smallest test that can answer the question.
Activity is kept inside the agreed budget. Evidence is captured as the test crosses each control. If the environment differs from the plan, that branch stops until the change is reviewed.
- 04
Handover
Check the final state and leave enough detail to repeat it.
The report separates observed facts from likely consequences and untested possibilities. Findings include the evidence, affected boundary, correction options and a short retest.
Rules used during the test
The short version.
- Written authority
- Only the named systems, accounts and actions are in scope.
- Production safety
- A proof that could damage data, availability or another user is staged and stopped.
- Data handling
- Evidence is limited to the material needed for the finding.
- Plan changes
- A new asset, privilege or technique is a scope change and needs approval.
- Cleanup
- Test markers and reversible changes are removed and recorded before close.
Before the call