docs: add CSV export formula-injection handling guidance

Document that provider CSV exports should be handled with formula-injection safety when opened in spreadsheet tooling.
2026-02-26 12:35:02 +00:00
parent 3d3493e546
commit ebea82f63d
2 changed files with 2 additions and 0 deletions
@@ -152,6 +152,7 @@ Provider user/project assignment views may exclude disabled projects even if his
 - Use exactly one client authentication method per token/control request (do not send both HTTP Basic and `client_secret` form fields together).
 - If you call provider WebAuthn login challenge/verify endpoints directly, use `POST` only.
 - Treat admin enrollment URL export as a state-changing operation: call it with `POST` and include a valid CSRF token.
+- Treat provider CSV exports as untrusted input in spreadsheet tools; prefer importing into systems that neutralise formula cells.
 - Configure OAuth client redirect URIs as HTTPS in production; reserve HTTP for localhost loopback testing only.
 - Assume provider rate limits are enforced per source identity (for example IP) and shared across related auth endpoints.
 - Treat report/export-style provider endpoints as high-cost and expect stricter rate limits.