1. BUG REGISTRATION

S.No.	Attribute	Entry
1	Safety Anomaly ID	CSM_BITS_ANM_0001
2	Bug Title	Login Issue
3	Bug Description	Unable to login/register successfully with valid user credentials.
4	Detection Source	User Report
5	Initial Evidence	Login/registration failure observed.
6	Reported By	Srikanth KS
7	Reported Date/Time	28-Aug-2026, 11:00 AM

2.INITIAL ASSESSMENT

S.No.	Attribute	Entry
1	Affected Item	CSM Web Application – Login / Registration
2	Version / Configuration	Deployed CSM application configuration
3	Anomaly Classification	Software / Application Issue
4	Safety Relevant?	No
5	Initial Safety Impact	No direct safety impact identified. The reported issue affects application login/registration functionality.
6	Responsible Person	AiSemi Engineering Team
7	Initial Evidence	Login/registration failure as reported by the user.
8	Initial Assessment Comment	The reported issue was reviewed and confirmed as a valid application issue. The anomaly was accepted for detailed analysis.
9	Replication / Triage Status	Confirmed / Accepted for Analysis
10	State Entry Date/Time	28-Aug-2026, 11:30 AM
11	State Exit Date/Time	28-Aug-2026, 12:15 PM

3.ANALYSIS & ROOT CAUSE ANALYSIS

S.No.	Attribute	Entry
1	Reproducible?	Yes
2	Reproduction Result	The reported login/registration issue was reproduced. Affected authentication and data persistence workflows were observed.
3	Reproduction Steps	1. Attempt login/registration using a valid user account. 2. Exercise the affected form/register/login/save flows. 3. Observe failure of affected POST requests. 4. Test authentication using a BITS email user when external authentication fails. 5. Observe that the expected local fallback authentication is not invoked.
4	Failure Mode	Valid user authentication, registration, or data persistence operations fail.
5	Failure Mechanism	Certain HTMX/AJAX POST requests did not reliably submit the required CSRF token, causing Django to reject the requests. BITS users were not handled equivalently to AiSemi users when external authentication failed, preventing the expected local authentication fallback.
6	Technical Analysis	Investigation identified two application-level implementation gaps. First, CSRF token submission was not handled reliably across the affected form, register, login and save POST flows. Second, the authentication flow did not provide local fallback authentication for BITS email users when external authentication failed.
7	Impact Analysis	The issue affected authentication and data persistence workflows, resulting in valid users being unable to login/register or complete affected save operations. No impact to safety analysis rules, ASIL values, or safety-related calculation logic was identified.
8	RCA Method	Technical Debugging / Application Flow Analysis
9	Root Cause	Incomplete CSRF token handling across affected HTMX/AJAX POST flows and incomplete local fallback authentication handling for BITS users.
10	Contributing Cause	CSRF handling and authentication fallback were not implemented consistently across all applicable request and user-account flows.
11	Verification Gap	Test coverage did not adequately cover CSRF handling across all affected form/register/login/save flows and local authentication fallback for BITS users when external authentication failed.
12	Analysis Conclusion	The reported issue was traced to two application-level implementation gaps: unreliable CSRF token submission and missing local authentication fallback for BITS users. Corrective actions were identified for both causes.
13	Analysis Evidence	Issue reproduction, application request-flow analysis, authentication-flow analysis, and identification of the affected CSRF and BITS authentication paths.
14	RCA Dependency / Delay	RCA required a test email for reproduction. The required test email was not received on 28-Aug, and detailed RCA was resumed on 29-Aug at 8:00 AM after the required test input became available.
15	State Entry Date/Time	29-Aug-2026, 8:00 AM
16	State Exit Date/Time	29-Aug-2026, 8:20 AM

4.CRITICALITY / SAFETY EVALUATION

S.No.	Attribute	Entry
1	Safety Goal Impact	No impact identified.
2	Safety Requirement Impact	No impact identified.
3	Safety Mechanism Impact	No impact identified.
4	Criticality	Low
5	ASIL Impact	No impact. ASIL values were not altered.
6	Risk Evaluation	The issue affected the authentication and data persistence workflow but did not alter safety analysis rules, ASIL values, or safety-related calculation logic.
7	Residual Risk	Low
8	Evaluation Rationale	The anomaly was limited to application authentication and data persistence functionality. No impact was identified on safety analysis rules, ASIL values, or safety-related calculation logic.
9	Evaluation Evidence	Technical analysis of the affected authentication and data persistence workflows and review of the impacted application functionality.
10	State Entry Date/Time	29-Aug-2026, 8:20 AM
11	State Exit Date/Time	29-Aug-2026, 8:35 AM

5.CONTAINMENT & CORRECTIVE ACTION

S.No.	Attribute	Entry
1	Containment Required?	No separate containment required.
2	Containment Action	Issue was addressed directly through corrective software changes.
3	Corrective Action	Ensure reliable CSRF token submission across form, register, login and save flows, and enable local fallback authentication for BITS users when external authentication fails.
4	Safety Measure	No product safety measure required. Application-level corrective action was implemented.
5	Change Required?	Yes
6	Change Reference	Software corrective change for CSRF handling and BITS local authentication fallback.
7	Action Owner	AiSemi Engineering Team
8	Implementation Status	Completed
9	Action Evidence	Code changes implemented for CSRF handling across affected flows and local fallback authentication for BITS users.
10	State Entry Date/Time	29-Aug-2026, 8:35 AM
11	State Exit Date/Time	29-Aug-2026, 8:50 AM

6.VERIFICATION & EFFECTIVENESS

S.No.	Attribute	Entry
1	Fix Verification	Corrective changes were verified for CSRF handling and BITS user authentication fallback.
2	Verification Method	Automated test cases and functional retesting of login/registration using a BITS email user on the live domain.
3	Verification Result	Pass. Login and registration flows completed successfully with the corrective changes.
4	Effectiveness Verified?	Yes
5	Residual Impact	No known residual impact identified.
6	Verification Conclusion	The corrective changes resolved the reported authentication and registration issue.
7	Verification Evidence	Automated test results and live-domain retest results for BITS email user login/registration.
8	Verifier	AiSemi Engineering Team
9	State Entry Date/Time	29-Aug-2026, 8:50 AM
10	State Exit Date/Time	29-Aug-2026, 8:57 AM

7.CLOSURE & APPROVAL

S.No.	Attribute	Entry
1	Closure Route	Corrective action implemented → verification completed → anomaly closed.
2	Safety Measure Adequate?	Yes. No product safety measure was required.
3	Effectiveness Verified?	Yes
4	Unreasonable Risk?	No
5	Closure Rationale	The reported authentication and registration issue was corrected and successfully verified. No impact was identified on safety analysis rules, ASIL values, or safety-related calculation logic.
6	Closure Evidence	Corrective software changes, automated test results, and live-domain retest results.
7	Rationale Reviewed?	Yes
8	Review Comments	Corrective action and verification evidence reviewed. The reported issue was adequately addressed.
9	Closure Decision	CLOSED
10	Reviewer	AiSemi Engineering Team
11	Final State	CLOSED
12	State Entry Date/Time	29-Aug-2026, 8:57 AM
13	State Exit Date/Time	29-Aug-2026, 9:00 AM