Project

General

Profile

Actions
Copy link

Story #34

open

Epic #51: Security Points Checking

Improper Error Handling

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

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

0%

Estimated time:
Acceptance Criteria:

1. Ensure that a customized error message is shown for any error that has occurred, which gives out very limited information.
2. Disable or limit detailed error handling. In particular, do not display debug information to end users, stack traces, or path information.
3. Application should make secure to prevent revealing of any kind of error and Hardening process should be carried out periodically.

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

Description

Prevent leakage of internal system details through error messages.

customizing error messages with limited information strikes a balance between informing users about issues and maintaining a user-friendly interface, all while safeguarding sensitive technical details.

Disabling or limiting detailed error handling involves configuring a system to refrain from displaying intricate technical information, such as debug information, stack traces, or file paths, to end users.

Actions
Copy link

Also available in: Atom PDF