syllabus.mdx 3.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. ---
  2. title: "Syllabus"
  3. description: "Syllabus, just to make sure we speak the same language. Those definitions apply in the context of Flowsint platform."
  4. category: "Overview"
  5. order: 2
  6. author: "Flowsint Team"
  7. tags: ["documentation", "overview", "syllabus"]
  8. version: "1.2.8"
  9. last_updated_at: "2026-05-15"
  10. ---
  11. ### OSINT
  12. Open Source Intelligence consists of collecting, analyzing, and exploiting **freely** and **openly** available information from search engines, images, social networks, public archives, etc.
  13. ### Investigation
  14. A structured process aimed at collecting, correlating, and analyzing information from different sources and enrichers, in order to answer a question or solve a problem. An investigation can be **exploratory** (discovering unknown elements) or **targeted** (validating a hypothesis). An investigation can contain multiple **sketches** (each representing a different view or stage of the analysis) and one or more **analyses**.
  15. ### Sketch
  16. Visual result produced by executing one or more enrichers on one or more entities. A sketch represents the current state of the graph derived from collected data at a given moment in the investigation. Multiple sketches can exist for the same investigation to capture different perspectives or stages.
  17. ### Analysis
  18. Set of processing, interpretations, and verifications performed on data collected during the investigation. Analyses aim to identify trends, confirm or refute hypotheses, and produce actionable conclusions. They can be **quantitative** (measurements, statistics) or **qualitative** (contextual assessments, behavioral patterns).
  19. ### Enricher
  20. An **enricher** is an operation that, from an input element **A** (*source entity*), allows obtaining one or more elements **B** (*target entities*) by applying a search or correlation method called a **pivot**.
  21. > Example:
  22. >
  23. >
  24. > A = `my.domain.com` (*domain name*)
  25. >
  26. > p = "DNS resolution" (*pivot*)
  27. >
  28. > B = `12.23.34.45` (*IP address*).
  29. >
  30. ### Pivot
  31. A **pivot** is the method or technical process used to derive **B** from **A**. The pivot defines **how** the enricher obtains its result (e.g., DNS resolution, WHOIS lookup, API query, etc.).
  32. > Examples of pivots:
  33. >
  34. > DNS Resolution → domain → IP
  35. > WHOIS Lookup → IP → owner
  36. > Reverse Image Search → image → web pages containing this image
  37. ### Tool
  38. A tool generally refers to a script, program, or service providing a **pivot**, i.e., a means to retrieve or enricher information from an input element.
  39. ### Entity
  40. An identifiable object or element manipulated by enrichers (e.g., IP address, domain, email address, user identifier, file hash, etc.). An entity is always associated with a **Sketch**. In the graph, entities are represented as **nodes** (see [Graph format](/docs/developers/graph-format) for technical details).
  41. ### Relationship
  42. Defines a link between two entities. This link is generally named (in uppercase) and can be unidirectional or bidirectional.
  43. > Examples of relationships:
  44. >
  45. >
  46. > A = `my.domain.com` → `RESOLVES_TO` → `12.23.34.45`
  47. >
  48. A relationship is always associated between a **source** node (*from*) and a **target** node (*to*). In the graph, relationships are represented as **edges** (see [Graph format](/docs/developers/graph-format) for technical details).
  49. ### Flow
  50. The chaining of multiple enrichers, where the output of one becomes the input of the next, allowing to expand or deepen an investigation.