Reports & Posture

The Reports & Posture page is Guara Shield’s at-a-glance summary of your account’s security posture. It answers: “how am I doing right now, and what’s driving the score?”

It is derived entirely from your Security Findings and Security Events. There is no separate scoring engine and no hidden logic. Everything that contributes to your score is something you could open in the Findings inbox or the Events timeline.

What you see

The page is organized around four blocks:

Posture score

A score expressing your current posture in plain language: strong, watch, or action needed. If Shield doesn’t yet have enough evidence to score honestly, you’ll see insufficient evidence instead of a fabricated grade.

The score moves on the inputs Shield can see today: open findings, severity distribution, recent resolutions, exposure changes, and how many recent observation windows have been clean.

What drives the score

A breakdown of the specific inputs that contributed to the current score:

• Open findings by severity.
• Findings resolved in the recent window.
• Active runtime risk signals.
• Recent risky exposure changes.
• Findings with confidence too low to weigh strongly.

Each input links back to the findings that produced it, so the score is never opaque. You can always click through to the underlying evidence.

Policy summaries

A summary of the security-relevant policies and defaults active on your account today, for example, that vulnerability scanning is enabled, that service scans run after every healthy deploy, that public exposure changes are tracked. This is descriptive, not configurable: it tells you what Shield is doing on your behalf today.

Report metadata

A small footer noting:

• When the posture was last computed.
• The window the score reflects.
• A reminder that Shield never stores raw request or response bodies.

”Insufficient evidence”

Many security tools always show a grade, even when the data behind it is thin. Shield refuses to do that.

If your account is brand new, or if there hasn’t been enough Shield activity to compute a meaningful score, the page will display insufficient evidence instead of strong. This is on purpose. A fake A+ would be worse than honest silence.

As Shield accumulates observation windows, the score becomes more confident. You don’t have to do anything to trigger this; just keep using Guara Cloud.

How the score behaves

A few principles for reading the score:

• Suppressed findings still cost you. Suppressing a known risk doesn’t erase the risk. The score reflects accepted-but-real findings.
• false_positive findings don’t cost you. That’s the whole point of marking them as false positives.
• A clean recent window improves the score. Posture is partly a function of how recently you’ve seen issues.
• Critical and high findings weigh much more than low and info. Don’t drown your score in low-severity hygiene noise.
• Confidence matters. Low-confidence findings contribute less to the score than high-confidence ones.

Reading and acting on the score

The score summarizes what’s happening; act on the underlying findings linked from each input. The posture page is your account’s own view, computed from your data and used only inside your dashboard.

How posture relates to other Shield surfaces

If your posture says…	Look here first
action needed	The open critical/high rows in Security Findings.
watch	The recent runtime signals and exposure changes on Security Events.
strong	Nothing urgent. The policy summary section is a good sanity-check anyway.
insufficient evidence	Give Shield a few more observation windows. New accounts naturally start here.

Where to go next

• Triage the findings driving the score: Security Findings.
• See the chronological inputs: Security Events.
• Scope down to one project or service: Project & Service Security.