Fictional product and launch case · Document 03
Discovery Findings and Sponsor Decision
The team records simulated findings and recommends a limited product-definition and technical-validation stage.
AegisShield Web Application Firewall · Discovery decision gate
AegisShield, BookEasy, the people, findings and decisions are fictional and created for portfolio demonstration.
Simulated customer findings
| Area | Finding | Implication |
|---|---|---|
| Current protection | BookEasy uses a basic hosted protection service and reviews alerts in more than one place. | A simpler view could help, but value is not proven for every customer. |
| Main pain point | The team needs to understand why a request was blocked and restore a legitimate booking quickly. | Event details, rule explanation and a safe exception path matter. |
| Ownership | Engineering configures protection while Support receives customer questions. | The product needs clear roles, permissions and escalation. |
| Pilot interest | BookEasy is open to a limited pilot if booking traffic is protected and rollback is ready. | The pilot is possible, but is not a purchase commitment. |
Recommendation
Authorize a limited product-definition and technical-validation stage for the AegisShield Firewall. The first version should use an established security engine and focus on one BookEasy web application.
The first version should cover application registration, a small set of rules, request and rule-match review, controlled block testing, a safe exception for a legitimate booking and an optional assessment of SIEM event integration.
Sponsor decision
Simulated decision: approve the limited product-definition and technical-validation stage. The approved boundary is one BookEasy web application, an established security engine, a limited set of rules, a controlled test environment and a pilot-readiness recommendation. Production protection, broad rollout and a proprietary engine are not approved.