dcsil / cyberity-app Goto Github PK

M - GET: employees(employee="") RETURNS: users
M - GET: allThreats() returns: List of threats
V Rest, M calender- GET: threatDashboardStats() returns: Stats object for dashboard (seperate function into smaller stats)
V - POST: GET: signup(user data) return: signed up or failure
V - POST: GET: login(user data) return: logged in or failure.
M - POST: setContained(user id)
V - GET: truePositiveRate() return: true positive rate
V - GET: priorityThreatList() return: get recent priority threats

This will require some well thought out feature selection and hyperparameter tuning.

List all the threats with the ability to sort by different attributes

Displays and obtains data on scroll or load more. This is to make the front end isn't storing/rendering the entire content result of fetch requests.

For example if there are 10000 users. Making react render or hold that many users in the front end would put a lot of stress on the server (we are doing server side rendering)

This feature displays user connections of threats, suspicious users and likelihood of user being affected by the incident. This feature is to allow security teams during their investigations to contain the insider threat.

create a modular dashboard component

Sub Components:

• Total/contained - past month - pie chart
• Live Threats - number
• Weekly/Monthly Threats - bar/line
• Daily threat calendar
• Tier list - Heuristics - Critical/Live -
• True Positives - Percentage bar
• How do the users know a threat has arrived?

Data processing functions at midnight for every user
-async processDailyData(BIG DATA,)
- Can be swapped out with log data processing on the serverside (currently dont have hardware to support this). Have pre simulated data
- getUserDailyStats(user, day)
- getUserDailyAverageStats(user)
- Can swapped out with how user implements. we going generate it ourselves by pre-process all the logs ourselves
- getGlobalStats()
- updateUserDailyAverageStatsWith(user, todays average)
- updateGlobalAverageStatsWith(global stats, todays average)
- model.apply(user daily stats, user average stats, global stats(everybody maybe departments/roles for future))
- If "yes" then add to live threats
- if "no" then pass

Retrain model every so often

(global average)

Also Add API routes if possible

Create user threats timelines and individual user event timelines

User threat timelines:

• Displays user threats in a timeline format. Can see previous and next user

Individual user event timelines

• Displays events of user before and after the occurrence of the the user being flagged as a threat. Helps with investigation

• Employees (Name, position, phone, email, tenure, stats(daily threats))
• Cyberity User (username, password, email)
• activethreats (user_id, detectionDate, status, priority (later))
• containedThreats (user_id, containedDate, status)

Later:

• User Log (Logs per user threat)

List of Customizable Features:

• New customizable display metrics in dashboard
• Drag placements of dashboard metrics
• resize of dashboard metrics
• Easy customizable ML model. Cater to the user.
• Give the user the power to modify themes

Congratulations on finishing the course. To make sure we have enough GitHub Actions minutes for the next term, we have automatically disabled your repositories actions.

Feel free to make this repo public or fork to your own org, but we do ask that you leave a copy in the DCSIL org :)

create a component to list and query all users within the system

create the main react page with the navbar used to swap out components

Ex. if we have slow query times for our users, we can move towards using Cassandra and our out database

create client side sign up and login page

Configure to setup for production and development purposes

Add routing for the application

Login page -> Home page with navbar -> all other pages