BiitOps DataLake

The BiitOps DataLake securely stores all collected configuration and asset data in its entirety, encrypted at rest

Each time new data is collected from an agent, it is compared to the previous version, and only changes are stored — following an “incremental forever” approach. This ensures storage efficiency while maintaining a full historical record.

Security and Encryption

The BiitOps DataLake securely stores all collected configuration and asset data with end-to-end encryption throughout its entire lifecycle. Data is encrypted locally on each device before transmission, remains encrypted during transfer via SSL, and stays encrypted at rest within the DataLake.

Decryption happens only when you pull data through the API - never during storage. This ensures your sensitive IT configuration information remains protected, accessible only through authorized API requests.

Storage Optimization

DataLake employs an intelligent delta-based storage approach - the lake never overflows. Each time new data is collected from an agent, it is compared to the previous version, and only changes are stored, following an "incremental forever" model.

The result: comprehensive historical visibility without storage explosion. Organizations can maintain complete change documentation for compliance requirements while keeping storage costs predictable and performance optimal.

Data Sovereignty

All data remains within your own environment throughout its entire lifecycle. BiitOps never hosts or transfers your configuration data to external systems - the DataLake exists entirely within your infrastructure or cloud tenant.

Your BiitOps instance automatically retrieves solution updates and licensing information from BiitOps online services - but never sends your IT configuration data outbound. This one-way communication ensures your sensitive infrastructure information stays exactly where it belongs: under your control.

Dual Timestamp Technology

Every property value in the DataLake has two distinct timestamps that work together to provide unprecedented data quality and confidence:​

Detected

When the property was initially recorded with its current value — establishing the baseline for this configuration state.

This timestamp answers: "When did this value first appear in our infrastructure?"

Example: User "jdoe" is member of "Domain Admins" - First Detected: 2024-02-01 10:15:00. You can document when this admin access was added.

Validated

When the property was most recently verified to still hold that same value — proving data freshness and active collection.

This timestamp answers: "How current is this information?"

Example: User "jdoe" is member of "Domain Admins" - Last Validated: 2024-10-23 08:30:00. You can confirm he still has admin access and this membership hasn't been revoked.

Why this matters:

Traditional IT systems leave you wondering: "Is this data from yesterday, last week, or last month?" You're forced to make decisions based on information of unknown age.

BiitOps eliminates this uncertainty. The Last Validated timestamp proves your data is current and your collection is actively working. You're not trusting assumptions - you're viewing verified facts with documented freshness.

Instead of "I think this is correct, but when did we last check?"
You get: "Verified this morning - and I can prove it."

Operational Benefits

For compliance auditors: Evidence of continuous monitoring with verifiable timestamps
For change managers: Clear identification of when configurations changed, supporting impact analysis

For security teams: Proof that security configurations remain in place between collection cycles

For operations teams: Confidence in using data for automation without fear of acting on stale information

“Now we have one source of truth — a unified asset database that has completely changed our foundation for work.”

Michael Lund Michaelsen, IT Consultant, Center for IT og Digitalisering, Frederikshavn Kommune

More information?

Download the DataLake whitepaper as PDF.

Data Retrieval

 

From the API, data can be retrieved as either Current State (latest confirmed values with Last Validated timestamps) or Historic States (all previous versions and changes over time with both Detected and Last Validated timestamps for each historical state).

This flexible retrieval model enables operational decisions based on current verified data, incident investigations using complete historical timelines, compliance documentation with verified evidence, and trend analysis across your infrastructure's history.

Ready to dive into the BiitOps DataLake?

Book a meeting to see how BiitOps gets you better insights