Feature Request - Inject Interface
Interface for injects: White Team:
- Ability to add new injects, or schedule injects for a specific time and date (and an expiration date / time but make it easy to set like +1 hour or +30 minutes, not a date/time selector, this way if it's published to the pending state early it will still only be good for an hour or 30 minutes)
- Ability to assign which teams (accounts) receive the injects (defaults to all - minus red team and white team)
- Injects should have a score and a default score configurable by the admin, but editable by the white team
- Injects should have 5 states
- Draft
- Scheduled
- Pending (in Blue Team hands)
- Submitted (when the blue team feels they have completed)
- Graded
- Injects should have a couple fields:
- Title
- Scenario
- Deliverable
- Scoring Rubric (just a table with 3 fields (0% 50% 100%) - This will be what the deliverable will be if they turn it in for 0, half, or full points.
- Each team should be able to see all of their injects with count down timers on the main screen for all of the injects. This should be replaced by their grade on the inject once it's been graded. (Timer -> Checkbox (submitted) -> Grade) or if they fail to submit anything (Timer -> 0% grade automatically with a "Not submitted" next to it)
- Each inject for each team should operate like a Github issue, with a box where the teams can add screen shots for proof and upload PDFs as well (no Word docs or Excel spreadsheets or other file types. PDF, Image, or text.
- Each inject can take multiple comments, and the white team or regional judges can make comments, the blue team has two buttons at the bottom of each inject - Comment and Submit
- The White team should see it in a grid pattern, with the ability to "grade" submitted injects:
| Inject Name | Time Left | Team 1 | Team 2 | Team 3 | Team 4 |
|---|---|---|---|---|---|
| Inject 1 | Expired | 50 (100%) | 50 (100%) | 25 (50%) | 0 (0%) |
| Inject 2 | Expired | 150 (100%) | Not Submitted | Not Submitted | 150 (100%) |
| Inject 3 | 0:20:15 | Grade Me! | Grade Me! | Pending (Comment!) | Pending |
| Inject 4 | 1:00:00 | ||||
| Inject 5 | Scheduled | ||||
| Inject 6 | Draft | ||||
| Inject 7 | Draft | ||||
| Sub Total | 200 | 50 | 25 | 150 | |
| Red Team Inject 1 | -100 | 0 | 0 | 0 | |
| Total | 100 | 50 | 25 | 150 |
(20 minutes left to submit Inject 3, and Inject 4 just went out)
- "Pending (Comment!)" means that the blue team has asked a question before submitting
- Red Team Injects are graded only by the White Team, and the Red Team can submit for any team, but they have to provide proof and can only submit for one team at a time.
- Regional judges should be able to log in and see their teams' injects and be able to grade them, the white team should be able to grade any submission as well as alter grades and see submissions
- Regional Judges should be like blue team logins with the only added benefit of being able to grade injects, and once graded, a regional judge should not be able to change a grade. That requires the white team to moderate and change.
- The totals should show on the main scoreboard just like the SLA scores, just another bar-chart
- There should be buttons for the respective actions, like "Add Inject" and "Add RT Inject"
- There should be a way to delete an inject
Can you give me some examples for an inject? What should the scenario/deliverable fields look like?
Also for the scoring rubric will it be something like the following?
0% - Not submitting at all
50% - Installing mongodb
100% - Installing mongodb and ingesting firewall logs
Something like this work?
ID: 5
State: Draft
Title: Journey to Mordor
Scenario: You have the ring, take it to be destroyed!
Deliverable: Word document in at least 3 volumes with journalistic evidence of each step of your journey and the destruction of the ring.
Scoring Rubric:
- 0: Damn hobbitses kept my precious!
- 50: You gave it your best effort, but died along the way.
- 100: You saved the world!
The rubric titles are shown to students and remote judges alike so they know what they are shooting for.
The title is just the short version of the scenario, the scenario sets the scene to what is happening and why, and the deliverable is what they have to return to get the score.