EBU Security self-scanning

[peterbrightwell]

See #642 for an overview of the planned workshop.

EBU Security Self-scanning

Monday 21 March – Wednesday 23 March

The EBU Security self-scanning track will follow the same structure as the NMOS Node, Registry and Controller Self-testing. After a demo on how to get the vulnerability scanner up and running, participants can scan their own equipment on their own schedule. The EBU Media Cybersecurity (MCS) group will provide assistance in case of technical difficulties with scanning.

The main purpose is to introduce participants to the possibilities of vulnerability scanners and encourage them to incorporate such tools in their product development and quality assurance processes if they haven't done so already. Also, this will help the MCS to further standardize the scanning methodology and improve their recommendations for the broadcast industry.

The results of a vulnerability scan could contain false positives and assessing the risk of actual vulnerabilities requires specific expertise. We recommend scheduling a follow-up call with one of the EBU MCS specialists to verify and evaluate the results of your vulnerability scan. They can also provide guidance on fixing or mitigating any detected vulnerabilities.

We guarantee the findings will not be shared with anyone else. If sufficient different devices are scanned, we would like to aggregate the results anonymously to know what types of vulnerabilities are most prevalent if the participants agree.

Prerequisites

The open source Greenbone vulnerability scanner will be available as a Docker container. To run the scanner, a machine with at least 4GB of RAM and some free storage space is needed. At the least, the scanning machine needs un-firewalled access to the device under test. The easiest way is for the scanner and the device under test to be on the same network segment.

Additionally, the scanning could set off security alerts in the company network, so it is best to use an isolated network.

Timetable

The self-scanning runs alongside the NMOS testing, and the two will share the Kick-off and Round Table times, and Slack channel. See #644 for more details of the tentative times (we expect the security kick-off to happen after the NMOS kickoff).