Web Auditing and Traceability

Auditing in the PostgreSYS platform is based on the generation and retention of logs that ensure the traceability of administrative operations. The PgSmart Web component acts as the central control point, recording who accessed the system, when the access occurred, and what modifications were applied to the environment.

Evidence Structure (Logs)

Operations performed through the web interface are persisted locally on the application server. These records are essential for forensic analysis and compliance verification.

info

To audit operations in the CLI Interface, refer to Auditing and Traceability on PgSmart CLI.

Log File Locations

Component	Default Directory	Main Log File	Logging Purpose
PgSmart Web	/var/log/pgsmart-web	pgsmart.log	Logs logins, changes to global configurations, and commands sent to agents.

Important

For security auditing purposes, access to this directory should be restricted to administrative users (root or specific sudoers) to ensure log integrity.

Security Note

It is recommended that this directory be monitored by SIEM (Security Information and Event Management)¹ to guarantee log immutability after generation.

Auditing Levels and Granularity

The platform allows adjustment of the level of information being logged in order to meet different compliance requirements.

It is possible to configure anything from basic detail levels (Info, Debug, Stack Trace) to explicit recording of operating system commands executed by the application.

Configuration

To adjust verbosity, enable OS command history, or configure log rotation, refer to PgSmart Web Log Configuration.

Log Lifecycle and Retention (Rotation)

To ensure the continued availability of audit evidence without compromising server storage, PgSmart Web implements automated rotation policies based on two criteria:

1. Time-based : Defines the periodic creation of new files (e.g. daily), facilitating event segmentation by date.
2. Size-based : Defines the maximum file size, preventing disk exhaustion in high-concurrency scenarios.

Configuration of these policies is performed directly in the administrative interface, as detailed in Log Configuration.

Audit Recommendation

For production environments subject to LGPD², access the Settings > Logs menu in PgSmart Web and set the Log Rotation Interval field to '1d' (daily). This ensures the temporal segregation required for efficient ingestion into SIEM¹ solutions.

Footnotes

1. SIEM (Security Information and Event Management) is a technological solution for automated log collection, normalization and intelligent correlation. It is widely adopted to support security controls such as PCI-DSS Requirement 10 (traceability and access monitoring) and ISO 27001 logging and retention controls, as well as assisting in compliance with LGPD and GDPR (European data protection regulation). ↩ ↩²

2. LGPD (Lei Geral de Proteção de Dados Pessoais) is the Brazilian Federal Law (13.709/2018) that regulates personal data processing. It requires the adoption of security measures for the protection and retention of audit logs, ensuring compliance and accountability. ↩