> For the complete documentation index, see [llms.txt](https://docs.invisiblebits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.invisiblebits.com/integration-of-data-sources/ingestion-architecture.md).

# Ingestion architecture

Data source integration is a core functionality of the platform, enabling seamless integration of any data source regardless of its location—whether situated within a client's private network, hosted publicly on the Internet, sending events directly from the cloud, running on a public cloud provider, or residing within a 5G telecommunications core.

The platform is designed with a 5 + 1 layer architecture, where each layer is responsible for providing services to its immediate upper and lower layers. This approach facilitates the construction of robust log shipping pipelines that include comprehensive error handling, layer-specific specialised mechanisms, and abstraction between layers.

<figure><img src="/files/bxOG06N8FThxSpqqsLcj" alt=""><figcaption><p>Multi-tenant log collection &#x26; shipping Ingestion architecture</p></figcaption></figure>

Below are detailed descriptions of the roles and mechanisms associated with each layer within the ingestion architecture:

<table data-header-hidden><thead><tr><th width="140.796875" align="center" valign="middle">Layer #</th><th width="188.40625" valign="middle">Role</th><th valign="middle">Functionalities</th></tr></thead><tbody><tr><td align="center" valign="middle"><strong>1</strong></td><td valign="middle">Local collection</td><td valign="middle"><p>· Local log collection in customer premises</p><p>· Local persistency</p><p>· Encryption &#x26; compression</p></td></tr><tr><td align="center" valign="middle"><strong>2</strong></td><td valign="middle">Shipping</td><td valign="middle"><p>· Shipping using one single TCP for all customer data sources</p><p>· Asymmetric encryption. Ensures confidentiality</p><p>· Compression. Reduces bandwidth</p></td></tr><tr><td align="center" valign="middle"><strong>3</strong></td><td valign="middle">Processing</td><td valign="middle"><p>· Processing of source formats</p><p>· Normalizing to standardized field names</p><p>· Enrichment &#x26; events contextualization</p></td></tr><tr><td align="center" valign="middle"><strong>4</strong></td><td valign="middle">Enrichment</td><td valign="middle"><p>· Matching against Threat Intelligence</p><p>· Contextualization</p><p>· Frameworks</p></td></tr><tr><td align="center" valign="middle"><strong>5</strong></td><td valign="middle">Data Lake</td><td valign="middle"><p>· Storage in Data Lake</p><p>· Second layer of detection use cases based in AI models</p><p>· Correlation &#x26; business analytics</p><p>· Visualizations &#x26; dashboarding</p></td></tr><tr><td align="center" valign="middle"><strong>6</strong></td><td valign="middle">Archiving</td><td valign="middle"><p>· Long term retention</p><p>· Restoration to live if required</p></td></tr></tbody></table>

Data source integration is managed from the **Integrations → Data Sources** section. This section provides the tools for integrating data sources, including:

* **Stream log ingestion** from sources located within clients' on-premises networks
* **Cloud services** located in the Internet, that send it's streams logs directly to the plateform
* **Public cloud platforms** such as AWS, Azure, and Google Cloud Platform

<figure><img src="/files/KoVpwedSHrSy0XsLJq2Z" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.invisiblebits.com/integration-of-data-sources/ingestion-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
