Password Policy
Employees must use strong passwords, avoid reuse, and update passwords from the account module when required.
Cyber Security Management System for Banking Sector
A database-driven PHP application to record, monitor, update, and manage banking cyber security incidents securely in Microsoft SQL Server.
High Risk Tickets
0Open Cases
0Monitor suspicious activity, ticket status, banking risk level, users, and SQL Server-backed incident records.
Please login to access protected modules.
All saved cyber security records
Need first review
Urgent banking security attention
Closed security cases
Submit suspicious banking activities such as phishing, unauthorized login, malware, fraud attempts, or data leakage.
Search, update, and manage cyber security ticket records stored directly in Microsoft SQL Server.
| ID | Date | Reporter | Branch | Type | Risk | Status | Updated | Action |
|---|
Create application users stored in SQL Server. Passwords are salted and hashed; login is validated on the server.
| Name | Username | Role | Status | Action |
|---|
Change your password and review your login details. All application records remain in Microsoft SQL Server.
Basic cyber security rules for safe digital banking operations.
Employees must use strong passwords, avoid reuse, and update passwords from the account module when required.
Do not open unknown banking links, attachments, or QR payment requests without verification.
Customer account information must not be shared through unsecured emails, public devices, or unverified websites.
High-risk and critical tickets should be escalated immediately and documented with action notes.