Sedara Web Application UI Design Challenge - II

Welcome to the Sedara Web Application UI Challenge - II. This project is for a cybersecurity services company that provides managed security services to customers, based on an overall program approach and attempts to cover all of the possible areas of security that they have deficiencies. This project is intended to design a public facing portal for Sedara that will provide a customer full visibility into the status of all of their Services that Sedara provides them.

This is a continuation challenge and we wanted you designers to come up with a solution for the next set of problems faced by the users;

• To manage, update and resolve the tickets
• Assess risk management based on provided statistics
• Maintenance of user accounts and company profiles

Make sure your designs comply with the existing designs.

CHALLENGE OBJECTIVE

• UI/UX design for web screens
• Design for 3 unique screen
• ?How well your design solves the problem and provides a seamless user experience.

Round 1

Submit your initial designs and any notes you might have for checkpoint review. 

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.)

• 01 Tickets Screen
• 02 Risk Management Screen

Round 2

Submit your initial designs plus checkpoint feedback implemented for the final review.

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

• 01 Tickets Screen
• 02 Risk Management Screen
• 03 Accounts Management Screen

PERSONAS: 
Marry Doe 

Job: CISO
Occupation: Executive in charge of overall security programs.  NON-TECHNICAL USER
Goals: Should be able to see the overall status of most components and identifiable value of Sedara services at a glance.  i.e. statistics showing the trend in risk going down over time
Frustrations: Too much technical content – they don’t want to get into the details
Wants: Quickly identify the status and actionable items that they need to push forward

 John Doe

Job: IT Manager
Occupation: In charge of operational IT within the organization, but may have a security responsibility in many organizations that don’t have a security team. 
Goals: Should be able to see the overall status of most components and identifiable value of Sedara services at a glance.  i.e. statistics showing the trend in risk going down over time
Frustrations: Too much technical content will create frustrations and not focus on the true status or next steps
Wants: Clearly identifiable action items and executive summary  

Rachel Stones

Job: Security Analyst (Customer Side)
Occupation: Very technical and hands-on role, in charge of performing security functions within the organization.  Generally not strategic in nature.
Goals: Ability to quickly drill into the details of each component, to be able to actually go and resolve identified issues.  i.e. if ‘Deployment Status’ for an endpoint is below 100%, they should be able to quickly get the list of systems that are missing, so they can go and install it.  
Frustrations: Inability to get to details of views or filter data quickly. 
Wants: Actionable and accurate data at their fingertips.  Ability to filter data quickly and export it into PDF or excel as a report. 
 

USER STORY:
Sedara’s customers spend a great deal of money for the services that we provide, but the deployment is always a moving target and security is never complete.
This portal is meant to give the customer a tool to regularly see the value in the services that we provide, the progress that they are making and the current deficiencies that they have. 

This portal should be a balance of reinforcing the positive commitments they have made in their overall security posture, while continually highlighting the risks that they still have and tie those back to either things that the Customer needs to do internally to fix or ways that Sedara can fix them for them. 


SCREENS / FEATURES REQUIREMENTS

For this challenge, we are looking for you to design below screens;

01 TICKETS:

View all tickets (Fields:  Ticket#, Creation Date, Subject, Priority [critical, high, med, low], status [open, resolved, pending assignment, etc.], requestor, Last updated Date)

• Need ability to sort by these fields
• ������Should have the ability to change status/close ticket from here – also close in bulk, but only by certain users

������Ticket details/update screen – drill into a single ticket to see more details and update it

1. Needs to show all available ticket fields
   - Fields:  Ticket#, Subject, Priority [critical, high, med, low], status [open, resolved, pending assignment, etc.], requestor and more fields as needed.

2. Easily show/search all updates on tickets – some of these may have several email’s back and forth – this needs to account for an easy way to show this – maybe it is a compressed view of each update – sorted chronologically and shows who updated it, but can click on each correspondence to expand and see the entire contents.  

3. Need text box to open/update tickets – should be able to drag/drop images or screen shots in here as well. 
   - Add a checkbox to open a ticket for ‘self’ or ‘All Team Members’ .  All Team Members are defined on the back end by Sedara. 
   - Adjust/Set Priority

02 RISK MANAGEMENT:

This should be another dashboard (like the main one) but will focus on more focused and discoverable content and the potential action items – both customer facing and Sedara

Sample Summaries – there are just examples and there may be many more to display, but these would likely be dashboard widgets and be flexible in how we show them.  

• Active Directory Users set with ‘password never expire’ 

• Show a count of the number of Domain Admin accounts (we will determine a ration of how many is too many, depending on the size of the org)

• Vulnerability Management Section – Show summary of top 10 vulnerabilities by asset
  - Should flag is no vulnerability scans are being run ( may need to be able to manually update/disable this or just remove the widget)

• Possibly a text based or bulleted ‘Account Notes’ section at the top that allows account managers or people to put notes in about the previous conversations and open items with risk in the account.
  - This might translate into a MOTD that gets displayed to analysts as well
  - i.e. this might have a note that the customer is planning a maintenance outage on a certain date, for everyone to be aware that their monitoring will go down at a certain time.
  - i.e. this may identify that they have an active penetration test going on that may cause additional alarms for us to be aware of.  

• List of High-Risk users, based on alarm activity or summaries.  i.e. users that are associated with many of the alarms

• Summary of removable media discovered in the environment – i.e. how many USB and flash drives have been discovered and are allowed to be used.  

• Identify and name shared accounts that have been identified with a notice to remove them and make individual accounts

03 ACCOUNT MANAGEMENT:

Account Management (Sedara Internal)

• View all customers (Sedara internal should be treated as an internal customer)

• Add Customers
  - Should be able to add a new organization/company and then add users to it
  - Fields (at least):  Org Name, Name, Email, Phone, Role,
  - Should be able to set notification types on each user (all alarms, high risk, operational, etc.)
  - Should be able to set permissions for users (global admin, Sedara Analyst, Sedara Read Only, Org Admin, Org Analyst, Org Read Only)
   

JUDGEMENT CRITERIA

• Creativity: Impactful; the solution is different or unique from what is already out there and can be implemented.
• Exploration: Out of the box; consider the screen requirements and guidelines as a draft or start point. Provide alternate experiences or workflows to achieve what we are proposing in the requirements and satisfy the user goals.
• Aesthetics: Hi-fidelity design; provide a top-notch finished-looking visual design.
• Branding: Follow existing branding guidelines / please see forums

DEVICE SPECIFICATIONS

• Desktop: 1366px width and Height as required
   

MARVEL PROTOTYPE

• We need you to upload your screens to Marvel App
• Please request for marvel app in the challenge forum
• You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment on this link while you upload) 
   

SUBMISSION AND SOURCE FILES
Submission File

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback
• Declaration files document contains the following information:

Source Files
All source files of all graphics created in either Adobe XD, Figma or Sketch.