Skip to main content
All CollectionsNavigating AssessmentsManaging Assessments
Viewing the Assessment Challenges page
Viewing the Assessment Challenges page

This article gives information to admins and managers with manager training permission on how to view the assessments Challenges page

FifthDomain avatar
Written by FifthDomain
Updated over 4 months ago

Overview

The "Assessment Challenges" page provides a comprehensive overview of all challenges featured within the assessment. Additionally, this page serves as a valuable resource for comprehending the specific cyber domains that are being evaluated in this assessment.

Depending on your access tier, you can add or remove challenges in this assessment from this page.

Section 1- Assessment profile

Skill Proficiency heatmap

This heatmap shows the skills that are being tested in this assessment in relation to the proficiency level.

The X-Axis shows the skills[1], and the professional specialty[2] it belongs to, and Y-axis represents the Proficiency level[3]. The blue-grey boxes[4] show which skill of what proficiency has been covered in this assessment. You can also hover over the boxes to the skill and proficiency combination it is representing.

Techniques and Technologies

  • Techniques refer to the specific methods or strategies required to resolve a challenge. For example, Metadata analysis, timestamp analysis etc

  • Technologies include the environments (e.g., Windows, Linux, Docker) and tools (e.g., Splunk, Nessus, Python) incorporated within the challenge, crucial for its resolution.

All the techniques/technologies in an assessment are listed in the bar graph[1] shown below. The length of the bar represents the weightage of that technique/technology in the assessment, and the number of segments on the bar represent the number of challenges the technique is a part of. You can hover over the bar segments to see the challenge name.

You can use Tabs[2] to switch between Techniques and Technologies. The number in parenthesis next to the title indicates the number of technologies/techniques.

Section 2- Challenges Table

Terminology

  • Professional Specialty-Professional specialties denote broad categories of cyber operations. Each challenge aligns with one of these specialties, providing a structured framework for classification.

  • Skills- Skills indicate the specific, acquired ability necessary to solve a challenge within a given timeframe or effort. Each challenge should necessitate one or two specific skills linked to the relevant professional specialty.

  • Techniques- Technologies include the environments (e.g., Windows, Linux, Docker) and tools (e.g., Splunk, Nessus, Python) incorporated within the challenge, crucial for its resolution.

  • Technologies-Techniques refer to the specific methods or strategies required to resolve a challenge. There is a preset list of techniques to select from, with the option to add more if needed.

  • Type- Type represents the format of the challenge. It could be either of the three:

    • Static: This format includes only static attachments like PDFs, markdown files, images etc

    • Lab-based: Lab based Challenges have lab environment attached

    • Container-based: Container based challenges have a link to a docker-container attached to them

The Challenges table has the following columns for important challenge details such as Challenges Name, Professional Specialty that the challenge belongs to, Type, Assigned Tags etc. You can see more details in the challenge drawer. The drawer can be opened by clicking the view button.

Challenge Drawer

The challenge drawer includes all the details of a challenge including:

  • Professional Specialty

  • Type

  • Estimated time to solve

  • Skills

  • Techniques

  • Technologies

  • Attachments

  • Lab attached

  • Assigned tags(depending on access tier)

  • Hints

πŸ“– Note: All labs in lab-based challenges have a duration of 2 hours. Participants can extend their lab instances as many times as they require, resetting their lab timers to 2 hours and retaining progress made. Participants can also reset their labs as needed, which will deploy a new lab instance and erase all progress.

Did this answer your question?