A.8.15 - Logging
Description
Requires companies to produce, store, protect and analyze records of relevant events. This enables companies to identify occurred or ongoing incidents, or identify trends and attempts to compromise information.
SIEM Compliance
In our ecosystem, data is stored in OpenSearch indices. Ensuring accountability for index deletion requires tracking the event across multiple layers of our stack.
When an index is deleted in Sentio, an audit trail is simultaneously recorded across three distinct layers, providing complete visibility into when the deletion happened, what was deleted, and who authorized the action.
Evidence
The HTTP Infrastructure Level (Web Proxy/API Gateway)
Every incoming request to the platform is recorded chronologically at the web server layer. This log captures the raw HTTP verb, the endpoint target, the network status code, and the processing duration.
Log Location:
/var/log/sentio/...(Flat File)What it proves: It verifies that a
DELETErequest was successfully received by the web server at a precise timestamp and executed with an HTTP 200 OK response.
The gateway registers the inbound DELETE /indices request with an explicit execution time marker.
The Web Application Level (Audit Database)
The Audit Database is the only log that explicitly binds the identity of the actor to the specific data asset that was destroyed.
Log Location: SQLite3 database at
/etc/sentio/sentio.dbWhat it proves: It maps the specific authenticated user account (
admin, user IDs) to the exact payloads ("indices":["test123"]) and explicitly logs that the confirmation was set totrueand acknowledged.
The internal audit database maps user admin to the destruction of the targeted test123 index asset.
The Data Storage Level (OpenSearch Engine)
The underlying database engine logs the physical execution of the deletion event from the cluster environment, confirming that the data blocks and metadata maps have been stripped from the system disk.
Log Location:
/var/log/elasticsearch/opensearch.log(Flat File)What it proves: It confirms that the OpenSearch cluster core (
MetadataDeleteIndexService) successfully dropped the index and its unique UUID string, triggering a cluster-wide state update.
The database backend validates that the index metadata and storage volumes were entirely purged from the host prod-data-1.
tags:
audit activity