Project

General

Profile

Actions

Story #39

open

Epic #38: Improper Handling of Case Sensitivity

Improper Handling of Case Sensitivity

Added by rashmita rout about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Medium
Assignee:
Target version:
-
Start date:
01/05/2026
Due date:
% Done:

0%

Estimated time:
Acceptance Criteria:

1. Implement Accept-Known-Good Input Validation
2. Reject or Normalize Non-Conforming Inputs
3. Enforce Case-Insensitive Comparison Where Applicable
4. Avoid Authorization Decisions Based on Resource Names

DOR:
No
Story Points:
Work Type:
Feature
User Impact:
Technical Area:
Release Narrative:
Planned Sprint:
Completed In Sprint:
Spillover Reason:

Description

"→Use an ""accept known good"" input validation strategy, i.e., use
a list of acceptable inputs that strictly conform to specifications. "
"→Reject any input that does not strictly conform to
specifications, or transform it into something that does."
"Avoid making decisions based on names of resources (e.g.
files) if those resources can have alternate names."

Actions #1

Updated by rashmita rout about 2 months ago

  • Assignee set to Tingg BE
Actions

Also available in: Atom PDF