You can find Platform Activity Reports by navigating to Reports in the main navigation menu and then Platform Activity.
This guide will outline the data points available in each dashboard and how they are calculated:
Overview
| Data point | Description |
| User activity | The percentage of users who have logged in, in the last 90 days. |
| Users not active for over 30 days |
The percentage of all individual users within your organization who have not logged in to the platform in the last 30 days or more. This only accounts for users who have registered and does not reflect remaining license allocation. |
| Managers not active for over 30 days | The percentage of all users assigned manager roles within your organization who have not logged in to the platform in the last 30 days or more. |
|
Highest difficulty level achieved by users
|
The percentage split of lab completions by difficulty. This is across all uses for the dates filtered. Lab difficulty ratings rate from one to nine, with one being the easiest. |
| Completions by area |
The total number of lab completions by content area/category, for the dates filtered. |
| Users with assigned content not started | The number of users who have collections and career paths assigned but have not yet launched any of the labs within them. |
| Users without content assigned |
Users who don't currently have any content assigned to them. Managers can assign Immersive Collections, Career Paths, as well as Custom Collections, to the whole organization, the team they manage, or individuals within the organization/team (depending on their system permissions). They can do this via the Manage Dashboard. Users can assign content to themselves by navigating to the lab collection or career path they wish to assign via the Upskill or Exercise menus. They can do this as a means of favoriting or bookmarking content.
|
| Newly assigned to users | The number of collections and career paths assigned to users per week. |
| Completed by users | The number of newly completed collections and career paths per week. |
| Last Crisis Sim exercise | The date an individual user last completed a Crisis Sim exercise. |
| Exercises in the last 12 months (Crisis Sim) | The total number of Crisis Sim exercises completed in the last 12 months. |
| Users with outstanding exercises (Workforce) | The number of users with Workforce exercises not completed. |
| Exercises in the last 12 months (Workforce) | The total number of Workforce exercises completed in the last 12 months. |
Platform usage
| Data point | Description |
| Licensed users | Total number of licenses used. |
| Users completed orientation | The percentage of licensed users who have completed platform onboarding and have supplied the relevant details about their role and usage. |
| Inactive users |
The percentage of all individual users within your organization who have not logged into the platform for the dates filtered.
|
| Inactive managers | The percentage of all managers within your organization who have not logged into the platform for the dates filtered. |
| Weekly lab activity | Graph depicting the number of users that have engaged with the platform on a weekly basis. This is separated into users attempting labs without completing, users completing at least one lab, and users that have logged in but not attempted any labs. |
| User logged in by type | The percentage of users that have logged in to the platform, broken down by system role/permissions against specific time periods. |
| Types of activity | The percentage split of users' activity by content/product type. |
| At least one lab attempted | The count of users who have attempted at least one lab in the platform within the dates filtered. This is displayed alongside the previous time period for comparison. |
| Average hours per lab per user | The average number of hours those who have started a lab have spent in the platform within the filtered date range. |
| Lab completion by area | A percentage split of activity by different lab content categories. |
| Average time in labs | Usage split by time spent in and out of working hours. Working hours are set as 9am-5pm within a specific user's time zone. |
| Monthly time in labs |
A visualization (bar chart) of the time spent in-hours and out-of-hours, split by month. Working hours are set as 9 a.m. - 5 p.m. within a specific user's time zone. |
| Crisis Sim participants | The number of participants across all Crisis Sim exercises within the selected date range. This is displayed alongside the previous time period for comparison. |
| Users completed workforce exercises | The total number of users that have completed assigned workforce exercises within the selected date range. This is displayed alongside the previous time period for comparison. |
| % Team Sim flags captured |
Within a Team Sim exercise, there are tasks to complete. When completed, a token will be revealed. We call these flags (from Capture The Flag). The flags should be entered in the answer boxes. This measure counts the number of correct flags/tokens entered. |
| Average hours in Team Sim | The average number of hours and minutes spent on Cyber Team Sim scenarios across the selected date range. This is displayed alongside the previous time period for comparison. |
| User list | A list of users limited to 50 rows, displaying products used, career paths assigned, last login and average time spent in the platform. The data on the list will reflect the filters selected. |
Assigned activity
| Data point | Description |
| In progress | The number of assigned collections that have been started by users but not completed. |
| Completed | The number of assigned collections that have been completed. |
| Not started | The number of assigned collections that have not yet been started. |
| Overdue | The number of assigned collections that are still outstanding and are past their due date (where this has been set by a manager). |
| Cumulative outstanding and complete | A view of the total cumulative number of collections both outstanding and completed over a specific time period. Outstanding collections are collections assigned that have not been completed. |
| Top 10 users with overdue assigned content | A list of 10 users in your organization with the most collections and career paths assigned to them in an overdue status (where a due date was set by a manager/admin). |
| Progress by content | The percentage of labs in collections and career paths completed by assigned users. |
| Progress by team | The percentage of labs in collections completed by team, and the time the team spent on those labs. |
| Progress by user | The percentage of labs in collections completed by users, and the time the user spent on those labs. |
Team overview
The calculations in the table are all for the date range selected in the filter (i.e. from the first date selected to and including the latest date in the range).
| Data point | Description |
| Active users (%) | The number of users in the team that have logged in at least once, divided by the team's total number of users. |
| Number of users | The total count of users licensed to access the platform (the denominator of all the % ages in this section). |
| Users attempting labs (%) | The number of users in the team that have attempted a lab at least once, divided by the number of users in the team. |
| Users completing labs (%) | The number of users in the team that have completed a lab at least once, divided by the number of users in the team. |
| Average hours in labs per users | The median total active time in lab attempts per user in the team. |
| Users with 0 completions (%) | The number of users in the team that have not completed any labs, divided by the number of users in the team. |
| Average completions per user | The median number of completions by users in the team. |
| Number of completions | The total number of attempt completions. |
| Attempts completed (%) | The number of completions divided by the number of attempts made per team. |
| Average accuracy (%) | The mean accuracy of completed labs per user, averaged across the team. |
| Average (Avg) difficulty | The mean difficulty lab completion for all users in the team. |
| Average max difficulty level | The mean highest difficulty lab completion for all users in the team. |
| Points earned | The total sum of points earned by users in the team. |
| Assigned content progress (%) | Content here includes all lab collections and career paths assigned. Progress is calculated as the number of assigned labs that have been completed, divided by the number of labs assigned, prior to or on the latest date in the range selected. |
| Number of users assigned | The number of users in the team that have had lab collections and/or career paths assigned to them. |
| Assigned content completed in period (%) | The number of assigned labs that have been completed during the date range, divided by the number of labs assigned prior to or on the latest date in the date range selected. |
| Users progressed assigned content in period (%) | The number of users that have completed at least one assigned lab during the date range, divided by the total number of users who have been assigned content prior to or on the latest date in the range selected. |
| Users completed all assignments (%) | The number of users that have completed all assigned labs by the latest date in the period, divided by the total number of users assigned content prior to the latest date in the range selected. |
| Never assigned (%) | The number of users that have never had assigned labs by the latest date in the period, divided by the total number of users in the team. |
| Number of assigned labs | The number of labs assigned to users in the team. |
| Cyber Capability score | A team's score is made up of two components (MITRE ATT&CK Score and CTI Score), each of equal weighting, added together. Each component is a score out of 500, giving a total score out of 1000. If a date range is selected, the score shown is the score at the first of the month of the latest month in the range. See below for details on how the two components are calculated. |
| MITRE Component |
How many users in a team have completed at least one lab in a technique, limited to five. If five users have, this gives a full score for the technique (25). If all techniques have been completed by five users, this gives a full score of 500. If a past date range is selected, the score shown is the score on the first of the month of the latest month in the range. The calculations only include labs the team has access to. |
| CTI component |
Points are awarded for the first five users to complete Cyber Threat Intelligence (CTI) labs published in the last six months, based on how close to the published date the user completed the lab. Each lab has a maximum score of 25. If all CTI labs published in the last six months are completed within seven days by five users, this gives a full score of 500. If a past date range is selected, the score shown is the score on the first of the month of the latest month in the range. The calculations only include labs the team has access to. |
Team comparison
| Number of teams without a team admin | The number of teams set up that do not have a Team Admin assigned to them. |
| Users to be assigned a team | The number of users that are not in any team. |
| Average number of users per team admin | How many individual users a Team Admin manages (on average). Calculated by: the total number of individual users divided by the total number of Team Admins. |
| Platform activity | A comparison of the percentage split of teams' platform activity by completion status. |
| Assigned content | A comparison of the percentage split of teams' assigned collections and career paths by completion status. |
| Workforce completions | The percentage of workforce exercises completed, out of those assigned. |
|
Crisis Sim completions |
The percentage of Crisis Sim exercises completed, out of those assigned. |
| Crisis Sim and Workforce engagement | The proportion of exercises assigned that have been completed, started, or not started. |
| Users connected to Team Sim |
Team Sim is an environment that is spun up by a user and closed down by a user. During the time it is up, any assigned users can connect to it, until it is shut down. This measure counts the number of users that have entered (or connected to) the Team Sim. |
| Team Sim flags captured |
Within a Team Sim exercise there are tasks to complete. When completed, a token will be revealed. We call these flags (from Capture The Flag). The flags should be entered in the answer boxes. This measure counts the number of correct flags/tokens entered. |
| Team Sim minutes connected |
Within a Team Sim, users that have been assigned to it can come and go as they please. This measure totals up how long assignees spent in the exercise (in minutes). |
Individual
| Labs completed | The number of labs completed by an individual user. |
| Badges earned | The number of badges earned (collections completed) by an individual user. |
| Team Sims participated in | The number of Team Sims an individual user has engaged with. |
| Lab accuracy | A list of 10 labs with the largest accuracy variance from an organization's average value of accuracy for the given lab. |
| Category coverage | Where and how a user is focusing their efforts. This includes lab content/category coverage, as well as level of proficiency. Proficiency level is based on the collection with the highest difficulty level completed, in a given content category. |
| Lab recommendations | Our recommender feature looks at labs the user has completed already and recommends adjacent content. |
| Assigned content progress | The completion status of collections assigned to a user. If they are spending longer on a collection than expected (based on the organization's average), variance will be positive. |
| Career path progress | The progress status of career paths a user has started and the time spent on them. |
| Collection progress | The progress status of collections a user has started and the time spent on them. |
| Labs in progress | A list of all labs a user has started but not completed, including time spent and when the lab was last visited by the user. |