Skip to main content

CAP.L0.SETTINGS_UNREADABLE — the server would not report its own configuration

  • Category: safety
  • Level: 0
  • Stability: stable
  • Suites: audit

The audit could not read the server's own configuration. Every rule that reasons about a server setting is left without a subject.

Why that needs saying out loud​

A rule with nothing to judge reports nothing. So does a rule that judged a correctly configured server. Without this notice those two outcomes are the same output, and the more alarming of them is the one that looks clean.

Their silence in this report means not checked, not fine.

Why it happens​

Most often a privilege: reading the full settings view is restricted, and on a managed database — the hosted PostgreSQL and MySQL offerings — that restriction is the ordinary case rather than a fault. It can also be a pooled session, where the settings read describes a backend the rest of the run never used.

What to do​

Grant the reading role access to the server's settings view if your platform allows it. If it does not, this notice is the honest end state: the schema findings above it are still true, and the server-baseline band is simply unanswerable on that platform.