Anomalies

Create Anomaly

  1. In the Administration tab select, Add New Anomaly.

    ../../_images/green_overview.png
  2. You can name the anomaly, create a time window for submission and determine a maximum score for the anomaly. The times are in 24 hr. format.

    ../../_images/create_anomaly.png

    Warning

    Anomalies that are marked required will automatically be marked accepted by all teams. This cannot be undone. The same applies if you are changing an anomaly from not required to required.

  3. Add a description and correct answer (grading instructions). Both fields support Markdown syntax.

  4. Specify what type of anomaly you want to create. See Anomaly Types for more information.

  5. Verify that your times are in 24 hr. format.

    Note

    It is possible to create anomalies that open before the start of the attack phase. This is supported, but IScorE will ask to confirm that you actually intend to do that.

  6. Click the blue Submit button to save the Anomaly.

Anomaly Types

New in version 1.5.

IScorE has the concept of Anomaly “types”. Currently there are three types “Basic Anomalies”, “Capture The Flag Anomalies”, and “Task Anomalies”. The differences between the types are described below.

Basic Anomalies
Normal anomalies. Have a description and a correct answer. Are NOT automatically graded.
Capture The Flag Anomalies
When blue teams submit this type of anomaly, their answer is compared against the anomaly answer and points are given automatically if they match exactly. Feedback is given to the blue team as to whether they have answered correctly or not. Incorrect answer are treated the same as normal anomalies to give graders the chance to give partial credit or to deal with any submission issues.
Task Anomalies
Anomalies that do not accept a submission. Normally used for anomalies that do not fit in with the standard Basic Anomaly format. Examples include crosswords and other “events” that teams get points for completing.

New in version 1.7: Task Anomalies were added in IScorE 1.7

Hiring Anomalies
Hiring anomalies are when blue teams are to tasked to add a new user to their systems. You will select the service and the user. The blue team will see the user on the anomaly submission screen. IScorE will check the credentials with given service at the expire time of the anomaly.

New in version 2.1: Hiring anomalies where added in IScorE 2.1

Firing Anomalies
Firing anomalies are when blue teams are to tasked to remove a user from their systems. You will select the service and the user. The blue team will see the user on the anomaly submission screen. IScorE will check the credentials with given service at the expire time of the anomaly. The fired users credentials are then leaked to the red team as the users ‘retaliation’.

Important

The error message for service must contain “authentication failed” (case-insensitive). Otherwise, the auto-grading will mark the service as up.

New in version 2.1: Hiring anomalies where added in IScorE 2.1

Note

The grading service is marked as admin down then the team will get zero points even if they passed the firing / hiring part of the anomaly.