Security Monitoring Tool Concepts Design Challenge

Welcome to “Security Monitoring Tool Concepts Design Challenge”! In this challenge we are looking to design a Security Monitoring Tool which would help to monitor the security devices. 

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit your initial designs for checkpoint feedback

• Login
• Dashboard
• Dashboard detail
• Individual device
• Device Onboarding

As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit your final designs with all checkpoint feedback implemented

• Login
• Dashboard
• Dashboard detail
• Individual device
• Device Onboarding
• Logs aggregation
• Reporting

As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
If you’re not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2
Challenge Objectives

• Design for a Responsive web application. (For this challenge, focus only for Desktop)
• Understanding the problem and providing an engaging solution

Project Background

Our client is a leading Security worldwide provider for enterprises serving their needs as well as governments in the public sector. They offer products that need to be monitored regularly for alerts and updates. They need to develop a web application to do monitoring for the product deployed at the customer base. 

This solution will be developed from scratch and will focus around SNMP (Simple Network Management Protocol) which is Internet Standard protocol for collecting and organizing information about managed devices on IP networks via a small set of SNMP query commands and SNMP traps. One can also gather additional details using native interfaces provided by the products.

General Design Requirements

• Check Challenge Forum for Network and Systems Management Reference
• We encourage you to do your own research about other NSM (Network and Systems Management) or Security Device Monitoring tools.
• Other than features/pages that we have listed below, please suggest any feature / elements that you think might be useful for the app.
• We are looking for an Intuitive, Easy-to-use, Professional and Modern design
• Present the data with least number of clicks. Data should be compact but in readable format
• Reduce scrolling as much as possible
• Create clear click-flow on your submissions to explain all pages and features
• Have a placeholder for Logo which will be replaced with actual logo during final fixes

Screen Requirements

1. Login

• Need to display these fields:
  • Username or email or Authentication ID
  • Password
  • Authentication service e.g, domain, local system, Azure, AWS or Google
• Add Forgot password & Register

2. Dashboard

• Device Management
  • Ability to add more than one device to be monitored
  • Ability to group them logically (Single level) and provide configurable labels for grouping
  • Suggest using dummy names such as SecureDev or even think of this security device as a compute server device with internal resources or metrics such as CPU util, memory, TPS, Network status, power / battery status, # active connections, etc that this tool will monitor.
  • We want ability to create logical groupings of these security devices based on configurable labels 
  • We want the ability to track these internal resources or metrics as an aggregate. For instance if we have 2 security devices in a group and the CPU utilization is 50% at the group/aggregate level. When we drill down on that group we want to see the individual CPU utilization of each of the 2 security devices, which could be 100% for one device and 0% for the other device in this example.
  • We want the ability to display based on the RBAC of the user logging in, Admin or Monitoring user.   
  • We want the ability to have status reporting of device and associated components so we can ‘follow the red’ to drill down on details. For instance if a device is showing high CPU utilization, we want to drill down some device specific info that could contribute to the high CPU util such as # of active connections, TPS, etc.
• Monitoring User
  • As monitoring user we want to have an easy to view dashboard with the following minimum items to quickly identify devices or services that require attention using non- authentication mode to the device or service to obtain the information
    • System configuration such as Security device serial number
    • Software version
    • Peak CPU utilisation
    • TPS (# of security operations)
    • Security device health such as temperature, battery status
  • Dashboard should support for high level view based on logical grouping
  • Must have the ability to click and get a detailed view on the individual monitored device. Device details need to load in the same screen, without a user going to different page

3. Dashboard Detail

• At the high level, we envision there are 3 ways to monitor the security devices

  • Graphical to show time series data such as CPU util, TPS
  • Static / Absolute values such as SN#, 
  • ���Status (Up/Down or Red/Yellow/Green based on thresholds) such as device connectivity, battery, temperature, etc

4. Individual Device
When user clicks on a particular device in dashboard, it takes them to the detailed view of the device

• User should be able to monitor device specific information

  • Software versions, 
  • IP address, port #s, # of active connections, 
  • last 10 events or logs generated
  • ���Hard drive, power supply, fans status
• Last 10 security operations or commands issued to security devices
• Monitoring maximum of 100 of this particular device

5. Device Onboarding
This page comes in during onboarding a user or system

• Must support a user profile (email address, phone number, preferred locale and others)
• Must support a user management password-for example for Monitoring users it would be Read-Only and for Administrators it would be Read/Write
• Group of security modules they are responsible for and to manage those (can have like hundreds or security modules or sub modules.) 
• What kind of alerts each user might want . Eg. through sms notification or through email etc

6. Logs Aggregation

• Need to visualise a way to showcase each security device logs
• Users should be able to archive these logs to save for future reference.
• Should be able to reload the logs
• Check all Logs History

7. Reporting

• Administrator should be able to view, save and print reports from pre-defined templates that come with the device / product 
• Should be able to generate PDF.  Be imaginative in terms of how to summarize the dashboard and the device specific reports. 
• Perhaps leverage typical compliance report or inventory report format/template

8. Other Screens

• Create how the alerts/notifications/success/error/warning are displayed in page
• GUI KIT (list all input, textarea, dropdown, modal, design elements, etc for guidance of future developers )

IMPORTANT

• Keep things consistent. This means all graphics styles should work together
• All of the graphics should have a similar feel and general aesthetic appearance

Marvel Prototype

• We need you to upload your screens to Marvel App for client review.
• Please send your marvel app request to lunarkid@copilots.topcoder.com
• You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).

Form Factors
Please make sure your design supports these form factors:

• In-scope
  • Desktop: 1366px(w) x Height up to your design
• Out of scope
  • Mobile and Tablet

Branding Guidelines

• Color Palette - Blue #0068B4 and any other color that would complement this blue
• Typography is opened to designers
• Stock photos and stock icons are allowed from the approved sources

Target Users

IT Administrator 

• He is an assembler who collects all user and system data
• He leverages what he’s done before, which means he will not rewrite anything. For eg. if he's configured a tool earlier, he would pull data from there on.
• He will be able to see all of the security devices

Monitoring Users

• With  the help of dashboard, he figures out the activities in the company, and provide sufficient information to the team responsible fo
• Answers questions regarding the module
• He will only see the specific group(s) of security devices this user is assigned for monitoring and alerting.

Judging Criteria

• How well you plan the user experience and capture your ideas visually.
• Cleanliness of your graphics and design.
• Overall design, UI and user experience.
• Consistency across the UX/UI.
• How well you interpret the features (business relevance) and show us new ideas and concepts.

SUBMISSION AND SOURCE FILES
Preview Image

• Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

 
Submission File

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback

Source Files

• All source files of all graphics created in either Adobe Photoshop, Illustrator, XD, or Sketch and saved as an editable layer

FINAL FIXES

• As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors.