AICI Demonstration Security Assessment

Web Application Penetration Testing Report

Public sample report showing how AICI structures management context, technical findings, remediation and retest expectations before a company buys a full assessment.

Public demo

AICI-DEMO-WEB-001

Training target

Executive overview

0

Critical

2

High

2

Medium

0

Low

Finding preview

HIGH

Authorization boundary requires remediation

Remediation guidance included

What a real client receives

EvidenceRemediationRetest

Demonstration environment — not a client engagement

This sample is based on OWASP Juice Shop, a deliberately insecure application created for security training, awareness and testing. No real client, customer system or third-party company is represented in this report.

OWASP Juice Shop project information

Report metadata

Report ID
AICI-DEMO-WEB-001
Target
OWASP Juice Shop training instance
Assessment type
Demonstration web application assessment
Data classification
Public demonstration

Scope and limitations

The purpose is to demonstrate report quality and remediation communication. It is not intended to reproduce every Juice Shop challenge, provide an exploitation guide or imply that the same findings exist in any production company.

Executive summary

The demonstration identified several weaknesses intentionally present in the training application. The highest-priority themes are authorization enforcement and safe handling of untrusted input. In a real engagement, AICI would validate affected assets within the signed Rules of Engagement, document evidence needed for remediation, and provide an agreed retest after fixes are deployed.

0

Critical

2

High

2

Medium

0

Low

Management priorities

  1. 0–7 daysAddress the demonstrated high-risk authorization and input-handling weaknesses in the training scenario.
  2. 8–30 daysStrengthen secure-development regression checks around role boundaries, input handling and output encoding.
  3. 31–90 daysIntegrate recurring authorized AppSec review into release planning and validate remediation with independent retesting.

Technical findings

This public version intentionally omits exploit payloads, sensitive reproduction detail and weaponized instructions. Real client reports contain sufficient authorized evidence for the client's remediation team and are handled as confidential security material.

AICI-DEMO-001

Broken access control exposes functions beyond the intended user role

High

Business / security impact

A user may be able to reach application actions or data that should be limited to a different role, increasing the risk of unauthorized changes or disclosure.

Evidence summary

Role boundaries were reviewed in the authorized training environment and a mismatch was documented between the intended authorization model and observed application behavior.

Recommended remediation

Enforce authorization on the server for every protected action and object. Do not rely on navigation visibility or client-side checks as an access-control boundary.

Retest expectation

Expected retest: verify denied access across affected role/object combinations after remediation.

AICI-DEMO-002

Untrusted input reaches a sensitive application operation without sufficient validation

High

Business / security impact

Improper handling of untrusted input can affect confidentiality, integrity or application behavior depending on the destination and privileges of the affected operation.

Evidence summary

A controlled training-only input path demonstrated that server-side validation and safe handling were insufficient for the affected operation.

Recommended remediation

Use parameterized operations, context-appropriate encoding and strict server-side validation. Add automated regression coverage for the affected input path.

Retest expectation

Expected retest: repeat the controlled input-validation checks and verify the unsafe behavior can no longer be reproduced.

AICI-DEMO-003

Security-relevant configuration exposes unnecessary application information

Medium

Business / security impact

Excessive technical detail can make reconnaissance easier and may reveal implementation information that is not required by legitimate users.

Evidence summary

Public responses in the training target included implementation detail beyond what was required for the user-facing workflow.

Recommended remediation

Reduce error and response detail in production, remove unnecessary banners or debug output and keep diagnostic information in protected server-side logs.

Retest expectation

Expected retest: confirm public responses no longer expose unnecessary implementation detail while operational logs retain useful diagnostics.

AICI-DEMO-004

Client-side output handling permits unsafe rendering of untrusted content

Medium

Business / security impact

Unsafe rendering of user-controlled content can affect user sessions, application trust and downstream actions performed in a victim's browser.

Evidence summary

A harmless marker in the intentionally vulnerable training application demonstrated that an output context did not apply the expected protection.

Recommended remediation

Use framework-safe rendering defaults, context-aware output encoding and a restrictive Content Security Policy as defense in depth.

Retest expectation

Expected retest: verify user-controlled values render as data rather than executable content across the affected contexts.

How AICI closes an engagement

A real engagement closes with scope confirmation, executive and technical reporting, remediation discussion, one agreed retest for the founding offer, and careful wording that reflects the tested scope and time period rather than claiming a system is “unhackable” or permanently secure.

Judge the deliverable before you buy the service.

Start with the free readiness score if AICI is new to you. If the company is ready for independent validation, apply for the full founding assessment at EGP 3,500 for the first three qualifying companies.