Story (Required)

An application/system can become unavailable for many reasons: an attack on the system (such as through a distributed denial of service attack, DDoS attack), improper allocation of resources, or over-reliance on a component that is likely to fail.

Some application vulnerabilities, such as allowing SQL injection, or cross-site scripting can increase the risk of denial of service. The weakness has two aspects: The system may not be protected against DoS attacks, and the system may not be well designed/implemented to continue to operate if its components fail (lack of a fallback mechanism).

Background (Required)

Refer to the Epic description.

Out of scope

Any previous counter measures.

Approach (Required)

- Discuss this issue in the bug triage or cabal.

Dependencies

NA

Acceptance Criteria (Mandatory)

• Bring this issue to the bug triage call and take a decision on the counter measure.
• If further discussion is needed, bring this issue to the cabal.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met