OSINT
Review agreed public sources to understand external exposure and how information could support an attack.
What we examine
Public footprint
Relevant domains, services and organisational information.
Exposure context
Assess the usefulness of public information to an attacker.
Evidence
Record sources and distinguish verified information from inference.
Actions
Prioritise practical changes to reduce unnecessary exposure.
Start with a research question
What can an outsider learn about your assets, staff-facing systems or technical footprint? We focus on that question and record the reliability of each relevant observation.
Information needed for a quote
Organisation names, domains, brands, business units and exclusions. Agree whether the exercise is passive public-source research only. Active checks and contact with people require a separately agreed scope.
Evidence included
Sources, dates and confidence, with an explanation of how the information could assist an attack. Old records and uncertain identity matches are labelled; recommendations focus on reducing useful exposure.
Scope, test, report.
Then verify the fixes.
Scoping, testing, reporting and verification, with direct access to the tester.
Agree the scope.
Applications, roles, access and deadlines. We agree the scope, fee and deliverables before testing.
Run the assessment.
Test the controls and the workflows around them. Significant findings are communicated during the engagement.
Document the findings.
Reproducible findings, demonstrated impact and practical recommendations for your developers.
Verify remediation.
Discuss remediation and validate agreed fixes. Retesting terms are set out in the proposal.