Security and data protection.

ArgusLogs runs in your .NET process and writes telemetry to sinks you configure. You control where data lives, how long it is retained, and who can access ArgusLogs.UI — there is no mandatory cloud ingest.

Data residency

Telemetry can remain on your infrastructure via file sinks, TieredStorage (SQLite hot tier + Parquet archives), or your own log platform. You choose what leaves the host.

Sensitive parameters

Mark parameters with [Sensitive] so values are not written in clear text in structured output. Review weaving rules before broad production enablement in regulated environments.

HTTP bodies

Request body capture is opt-in (for example NetworkTracker WithLogBody). Bodies can contain secrets and PII — leave this off unless you have a retention and access plan.

Headers

Header capture is opt-in (WithLogHeaders). Authorization and cookie headers are high risk; prefer redaction and least privilege.

Cookies

Cookie capture is opt-in and commonly left off (WithLogCookies false in public samples) because cookies are often session or auth material.

SQL

When database tracking is enabled, SQL text and parameters can appear in telemetry. Treat that store like a database backup: encrypt at rest if your policy requires it, and limit who can query it.

Storage

Files and TieredStorage live where you configure them. There is no mandatory ArgusLogs cloud ingest. Lock down disk and object-store ACLs the same way you would for application data.

Retention

Configure retention in TieredStorage and cap UI query limits. See /best-practices/retention.

ArgusLogs.UI authentication

In production, protect /argus-logs with RequireLogin, strong passwords, and optional localhost-only filters. Examples: /best-practices/secure-ui.

Production deploy

Do not expose /argus-logs on the public internet without auth. Prefer Development keys on developer machines and Production keys on servers; keep keys out of source control. Generator: /get-license.