BS

BankShield

Cyber Security Management System for Banking Sector

Student Project - BCA VI Semester

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.

Student Name: Navya Sharma
Class: BCA VI Semester
Storage: Microsoft SQL Server database
🛡️ 🔐 💳 🏦 ⚠️

High Risk Tickets

0

Open Cases

0
Admin Overview

Cyber Security Dashboard

Monitor suspicious activity, ticket status, banking risk level, users, and SQL Server-backed incident records.

Logged in user

Not logged in

Please login to access protected modules.

Total Tickets 0

All saved cyber security records

Pending 0

Need first review

High Risk 0

Urgent banking security attention

Resolved 0

Closed security cases

Risk Distribution

Status Summary

Security Checklist

  • Verify suspicious customer transaction alerts.
  • Block phishing links and fake banking portals.
  • Escalate high-risk tickets to security administrators.
  • Review branch-level login activity and staff device reports.
  • Use SQL Server backup procedures for production backups; JSON export is provided only as a portable report snapshot.
User Panel

Create New Security Ticket

Submit suspicious banking activities such as phishing, unauthorized login, malware, fraud attempts, or data leakage.

Case Management

Ticket Records

Search, update, and manage cyber security ticket records stored directly in Microsoft SQL Server.

ID Date Reporter Branch Type Risk Status Updated Action
Admin Module

User Management

Create application users stored in SQL Server. Passwords are salted and hashed; login is validated on the server.

Add New User

Saved Users

NameUsernameRoleStatusAction
My Account

Profile & Password

Change your password and review your login details. All application records remain in Microsoft SQL Server.

Current User

Change Password

Awareness

Banking Cyber Security Policies

Basic cyber security rules for safe digital banking operations.

Password Policy

Employees must use strong passwords, avoid reuse, and update passwords from the account module when required.

Phishing Protection

Do not open unknown banking links, attachments, or QR payment requests without verification.

Data Privacy

Customer account information must not be shared through unsecured emails, public devices, or unverified websites.

Incident Response

High-risk and critical tickets should be escalated immediately and documented with action notes.