Review app security
The Security tab of an app collects what you need to judge its exposure in one place: settings that put it at risk, known vulnerabilities in its image, and suspicious requests that reach it. Each finding links to the setting that fixes it.
To open the tab, open the app and select Security.
Configuration
Section titled “Configuration”The Configuration card checks the app’s settings. These checks do not need a scanner.
| Finding | Meaning | How to resolve |
|---|---|---|
| Secrets in plain variables | A variable name looks like a secret, and the value is stored as plain text. | Select Variables, then store the value as a secret. |
| Served over plain HTTP | A domain on the app has no TLS and is not a redirect. | Select Network, edit the domain, then turn on HTTPS. |
| Image tag can change | The image uses a tag that can point to a different image, such as latest. | Select Source, then set a fixed tag. |
When there are no findings, the card shows Nothing to flag.
Image scan
Section titled “Image scan”The Image scan card lists known vulnerabilities in the app’s container image. A superadmin must set up a scanner on the instance.
To run a scan, select Scan now or Scan again.
| Message | Meaning |
|---|---|
No known vulnerabilities | The scan found no known vulnerabilities. |
Not scanned yet | No scan has run for this image. |
The last scan failed | The scan did not finish. The card shows the error. |
Image scanning is off | No scanner is selected on this instance. |
Scanning isn't set up on this instance | A scanner is selected, but its credentials or server are missing. |
Harbor only scans images Orchard builds | The app uses an external image, and the instance uses Harbor. |
This image is no longer in the registry | The image was removed from the registry. Redeploy to build and scan it again. |
The scanner refused Orchard | The scanner rejected the credentials. |
Can't reach the scanner | Orchard cannot connect to the scanner. |
Attack attempts
Section titled “Attack attempts”The Attack attempts chart and the Top sources list show suspicious requests from the last 24 hours. Orchard finds these requests in the ingress access logs. Orchard records them, but does not block them.
| Category | Condition |
|---|---|
| Scanners | The path targets a common probe location, such as /.env, /wp-admin, or /.git, or the user agent is a known scanning tool. |
| Injection | The path contains an SQL injection, path traversal, script injection, or JNDI lookup pattern. |
| Password guessing | One client address receives at least 21 401 or 403 responses from one path within 5 minutes. |
| Floods | One client address sends at least 300 requests, and more than 10 times the median of all clients. This check needs at least 5 client addresses. |
If the card shows Requests aren't recorded yet, the log store has no access logs for the app. To set up access logs, refer to Configure logs and request data.
The Top sources list can show the row Hidden by the load balancer. This row groups private and cluster addresses, which usually means the load balancer hides the real client address. To fix it, refer to Client IPs show as hidden.
Related resources
Section titled “Related resources”- Protect an app - Require a sign-in or a password before a domain opens.
- Turn on bot protection - Add a Cloudflare Turnstile challenge to sign-in pages and password-protected apps.