Not sure where to start?

Start with free introductory courses

Create account

Illustrative training artifact

What a clear security finding should communicate.

This page demonstrates the structure and writing quality expected in an AICI learning report: scope, evidence summary, risk, impact and remediation.

Important: this is an illustrative training sample, not a client report, not evidence of a real assessment and not a claim that these findings exist on any public system.

Reporting workflow

1. Confirm written scope and authorization.
2. Reproduce only what is necessary to validate the observation.
3. Preserve concise evidence without exposing unnecessary sensitive data.
4. Explain impact without exaggeration.
5. Recommend practical remediation.
6. Retest after an approved fix when retesting is in scope.

Example findings

A finding should be understandable without a live exploit demonstration.

Finding 01

Broken object-level authorization

High · illustrative

Observation

In the example lab scenario, a standard test account can request a record assigned to another lab user because the server-side authorization check is incomplete.

Potential impact

A real issue of this type could expose data to an authenticated user who should not be allowed to access it.

Remediation

Enforce server-side authorization on every object request, deny access by default, and add automated tests for cross-user access boundaries.

Finding 02

Insufficient login rate limiting

Medium · illustrative

Observation

The example lab login flow accepts repeated failed authentication attempts without an effective throttling response.

Potential impact

In a real environment, insufficient rate controls can increase exposure to automated password-guessing attempts.

Remediation

Apply risk-appropriate rate limiting, monitoring and lockout controls while avoiding denial-of-service conditions for legitimate users.

Finding 03

Incomplete browser security headers

Low · illustrative

Observation

The example response is missing selected browser security headers used to reduce exposure to certain client-side attack classes.

Potential impact

The missing controls can reduce defense in depth even when no direct exploit is demonstrated by the observation alone.

Remediation

Define an application-appropriate header policy, test it before release and monitor for regressions.

Technical skill is only part of the deliverable.

A professional security report should help an authorized stakeholder understand what happened, why it matters, what evidence supports the conclusion and what action should happen next.