Skip to content

AI prompt · OSINT

Prompt: OSINT collection plan for an authorised engagement

Prompt that builds an OSINT collection plan for an authorised engagement: objectives, sources by category, tools, legal limits and deliverables.

By Steven Carrier Published

Works with: Claude, other chat assistants

You are an OSINT analyst working under an authorised contract. Build the collection plan for the engagement described below.

Authorised target: {{authorised_target}}
Engagement objectives: {{objectives}}
Constraints: {{constraints}}

The plan includes:
1. objectives restated as precise intelligence questions, with the criterion that tells you a question has been answered;
2. sources by category (public and company registers, domain names and DNS, certificates and transparency logs, search engines, professional social networks, public code repositories, news and archives), with what you expect to find in each;
3. tools or methods for each category, staying on open sources;
4. legal and ethical limits: passive collection only, unless explicit written authorisation covers any interaction with the target; minimisation of personal data under the GDPR (collect only what serves an objective; exclude sensitive data and people's private lives); respect for platform terms of use;
5. collection organisation: order of steps, logging of sources and dates, retention period and deletion of data;
6. deliverables: report format, confidence level of the information, presentation of sources.

Do not propose any unauthorised access, impersonation or social engineering method. If an objective requires going beyond passive or authorised collection, flag it rather than work around it.

Replace the highlighted variables before use.

An OSINT engagement without a plan quickly drifts: redundant sources, personal data collected for no reason, an unreadable report. This prompt helps structure the collection before you start, from a scope already agreed with the client. It builds on the same scoping foundation as the penetration test scoping checklist.

Fill in the variables

Variable Example
{{authorised_target}} Example Ltd (domain example.com), scope approved in writing by the legal representative, excluding employees in a private capacity
{{objectives}} map the publicly exposed footprint, identify leaked documents and code repositories, assess executives’ exposure to impersonation
{{constraints}} passive collection only, two weeks, no contact with the target, data retention limited to the duration of the engagement

The authorised scope must exist before this prompt: it is decided with the client, not with the model.

Review the output

  • Check that the plan stays passive and within scope: remove any action that implies interaction with the target or its employees.
  • Check minimisation: each piece of personal data collected must serve an objective of the engagement. Have the plan reviewed by your data protection officer or legal contact if in doubt.
  • Check the terms of use of the platforms named: automated collection is sometimes prohibited there.
  • Check that each tool or source proposed exists and is still available: a model sometimes recommends defunct or paid services.
  • Do not paste into the prompt any client data or personal data that your engagement agreement does not allow you to share with an AI service; describe the target in general terms if necessary.

Sources

Related resources

  • AI prompt · Infrastructure and AD pentesting · OSINT · Cloud

    Attack surface prompt

    Prompt that analyses an asset inventory from the authorised scope (domains, IPs, services, cloud) to prioritise testing: exposure, criticality, checks.

    Published

  • Cheatsheet · OSINT

    Domain OSINT cheatsheet

    Passive collection on an organisation’s domain: whois and RDAP, DNS with dig, certificate transparency, subdomains, SPF and DMARC records.

    Published

  • Methodology · OSINT

    Organisation OSINT exposure

    Methodology to assess an organisation’s OSINT exposure for an authorised client: legal framework, infrastructure, people, leaks, code, brand, reporting.

    Published

BEAROPS

Need an OSINT investigation?

BEAROPS carries out OSINT investigations lasting from a few days to several weeks, using open sources within a legal framework.