The docs tree is laid out like the menus - a menu path is a docs path. Admin Panel / Settings follows the new structure: Visibility.md is Appearance.md, with new Features.md, Feature-Profiles.md, Security.md, Activities-and-Notifications.md and Delete.md; the section indexes, Admin-Panel.md, Admin-Panel-URLs.md (with the moved-pane redirects) and Validation.md follow the live menus, and Who-Sees-What.md explains in one place which layer decides what is shown and what is allowed. Pages are added for the menu entries that had none, each written from the code: every Admin Panel / Problems pane, the member menu, the board header, Board Settings, the All Boards left menu, and the list, swimlane and card menus. Older links to the moved panes are updated across docs/. TODO.md records what documenting the menus found: Edit Profile does not save a username for non-admins, the Support page's signed-out case is unreachable, Create board from this card is hidden from members who can edit the card, All Boards Settings is unreachable, and the Share template targets live in browser storage. Thanks to xet7 !
3.7 KiB
Admin Panel / Problems / Security Report
Every attempt a security guard refused or noticed: what it was, how severe,
who tried it, from where and how many times. Address:
/admin/problems/security-report. Site administrators only. It is called
Security Report, not Security, because Admin Panel / Settings /
Security is the pane of security switches.
Where the rows come from
The security stream of the eventlog collection (models/eventLog.js).
Every runtime guard reports through server/lib/securityLog.js when it blocks,
sanitizes, rate-limits or detects something, using a key from the catalog in
models/lib/securityCategories.js (category, Hall of Fame name, severity,
CWE). Besides the guards, this stream also receives:
- the canaries - operations WeKan never issues, such as a database canary
marked by FerretDB (
server/lib/databaseProblems.js); - the daily filesystem integrity scan's findings (
integrity.file, StorageBleed,server/lib/fileIntegrityScan.js) and the hourly change history audit (integrity.history, HistoryIntegrity,server/lib/historyIntegrityScan.js); - denied passwordless code requests after five requests per source address in one minute;
- the Meteor 3.5.3 refusals, recorded as Meteor DDP, Meteor allow-deny, Meteor dynamic-import and Meteor OAuth (details);
- ImportExportValidation (an import or export refused by the transfer boundary) and ImportExportFailure (one that failed for another reason, recorded as detected, never as an attempt).
Each problem is one row that accumulates (server/lib/eventLogFold.js): the
kind of thing that happened is the row, and the user name and address describe
its most recent occurrence (Design.md).
Consequence for the account
When a row is blocked, of severity high or critical, names a logged-in
user and its catalog key does not say otherwise, that account is disabled
(loginDisabled) with the reason "Attempted at while logged
in" (server/lib/blockOnSecurityEvent.js). The address is recorded, never
blocked. An administrator re-enables the account in Admin Panel /
People.
The table
The shared table page, newest row first, 10 rows a page, read-only:
| Column | Holds |
|---|---|
| Date and time | when it last happened |
| Category | the guard's class, for example ssrf or integrity |
| Name | the Hall of Fame name (...Bleed) or another fixed name |
| Severity | info, low, medium, high or critical |
| Action | blocked, sanitized, rate-limited, remediated, detected or failed |
| Source | the guard or module that recorded it |
| Username | the account, as it was called at the time; click it for the Edit user popup |
| IPv4, Location, IPv6, Location | the address, resolved with HTTP_FORWARDED_COUNT, and a location only when a trusted proxy supplies one |
| Attempts | how many times this row happened; empty when once |
| Detail | what the guard said |
The search box filters as you type, case-insensitively, over category, name,
source, detail, username and address. The rows come from the admin-only
eventLogCount and eventLogPage methods.
Nothing is acknowledged here: the new-problem count is acknowledged or the
stream cleared on Summary. Rows older than
EVENTLOG_RETENTION_DAYS (default 90) are deleted daily. The same rows are on
GET /api/admin/problems/security
(REST API).
Related
- Security remediation design
- Hall of Fame - the names in the Name column.