Crowd and Capacity Monitoring

Home/Crowd and Capacity Monitoring
Crowd Management and Communication

Crowd Management and Communication

2020-03-31T12:09:28+02:00

Crowd Management and Communication Crowd management and response is greatly facilitated by the MONICA Crowd Management and Communication solution. This solution gives a perfect overview of event activities in real time as well as means for feed-back to and communication with security and first-responder staff in the field. This solution complements the MONICA Crowd [...]

Learn More
Pützschens Markt Crowd
Crowd and Capacity Monitoring

Crowd and Capacity Monitoring

2020-04-19T14:49:21+02:00

Crowd and Capacity Monitoring The MONICA Crowd and Capacity Monitoring solution is used by Smart City organisers, event organisers, security staff and first responders to monitor crowd behaviour and manage security at large events, e.g. to mitigate security and safety risk or annoyance. This MONICA solution complements the MONICA Crowd Management and Communication solution. [...]

Learn More
© Copyright 2017- | The MONICA Project | All Rights Reserved |

CMC-2 Crowd Managment and Communication
Security, Privacy and Trust Framework
 

The aim of cyber security, privacy and trust framework is to address the privacy and security of technical issues within the MONICA IoT infrastructure, which is expected to share critical information with components involved in the pilot sites. The protection implementation has been determined based on the assessment of cyber risks that the ICT infrastructure of pilot sites can be exposed to during the integration of the MONICA IoT infrastructure. To tackle these challenges, security implementations need to be defined within the IoT architecture. Hence, the following MONICA high-level security protection implementation policy have been implemented and can be implemented in the architecture specification.

High-Level Security Protection Implementation Policy

  • Access Control: This process detects and prevents unauthorized access and permit authorized access to information asset within the IoT architecture. The access control standard such as ISO/IEC 27002 provides the requirements surrounding the management of access to information.
  • Device Authentication: This process provides security mechanism within the IoT architecture and ensures that only authorized devices can be authenticated and connected to a given RESTful interface or network.
  • Certificate Authorization: This process provides authorization of certificate sharing between IoT devices within the IoT architecture to ensure message/information integrity.
  • HTTPS connection on RESTful interface: A secure https is used for sharing and connecting to the public interface and the MONICA cloud infrastructure.
  • Data Encryption: This process encodes message/information that is shared between devices and the IoT infrastructure. Keys to decrypt such message or information share legitimately as well.
  • Data Masking: This process transforms affected personal data on application/database level to comply with legislative requirements of EU/EC. To be applied by anonymization resp. pseudonymisation of processed personal identifiable information related to affected visitors resp. staff.
  • Technical vulnerability management (aliter patch management): This process ensures that published information about technical vulnerabilities of IoT infrastructure (e.g. CVE*) shall be obtained in a timely fashion, the exposure to such vulnerabilities evaluated and appropriate measures taken.
  • Logging and monitoring: This process ensures that event logs recording user activities, exceptions, faults and information security events should be produced, kept and regularly reviewed (with special focus to system admin and operators). Logging facilities and log information are protected against tampering and unauthorized access; Clock synchronized;
  • Endpoint protection: This process ensures protection from distributed vulnerabilities based on the “human factor” – users/administrators of workstations/servers, and reflect the principle, that project MONICA must not rely only on peripheral defence for the whole security. Each desktop and server MUST also be protected by the current approved products (typically Anti-Virus, Firewall and Anti-Spyware).
  • Network controls: This process ensures that technical network issues shall be addressed and maintained (to protect information in systems and applications; Security mechanisms, service levels and management requirements of all network services shall be identified and included in network services agreements; Groups of information services, users and information systems shall be segregated);
  • Information transfer: This process ensures that the network issues related to Personal Data Protection shall be addressed and maintained;
  • Backup and Redundancies: These processes ensure IoT availability/connectivity (resp. protect against loss of data).
  • Technical compliance review (aliter Penetration testing): This process ensures that the IoT infrastructure is regularly reviewed for effective compliance with the requirements of enlisted processes resp. IT Security Baselines by automation tools resp. applications.

Security, Privacy and Trust Framework

The MONICA Cyber Security Privacy and Trust Framework Architecture

CMC-2 Crowd Managment and Communication
Common Operational Picture (COP)
 

In the event control room, the Common Operational Picture (COP) will be used on multiple large screens, one dashboard for each focus area (e.g, security, sound, feedback). The Event Manager is the stakeholder leading the event who needs to have control over all areas of the event. Then there are more specialised stakeholders that focus on one or a few areas, such as police (security), fire brigade (security), first aid (health related events), head of security (security, lead guards), sound control (sound). The COP is comprised of three main components:

  • The COP Dashboard: This is used for the end user visualisation and overview.
  • The COP Database: This database contains COP related information and acts in a certain extent as a data cache.
  • COP Updater: This component is responsible for updating the COP with regards to the data streams available in the MONICA platform.

Dashboard: The COP dashboard is a component deployed in a Docker container in the MONICA cloud running Node.js. The actual dashboard is a normal web app running in a browser. The COP dashboard uses the Open IoT APIs of the MONICA IoT platform to retrieve and display information from the MONICA devices.

COP at the Nuits Soneres in Lyon 2018 © CNet

The COP displaying crowd data and staff positions during Nuits Soneres 2018 in Lyon

Database: The COP Database manages the information needed to maintain the Common Operational Picture, though it also contains additional information, for instance, it has a cache of the latest values from the different data streams available in the MONICA platform. The database is deployed in a PostgreSQL cluster in the MONICA Cloud. The COP database is also the base for the MONICA professional API.

COP Updater © CNet

The COP Updater

Updater: The COP Updater module manages updates to the COP database with regards to which data streams are available in runtime in the MONICA system. It also manages the latest value cache for all data streams that are of interest for the COP.

The main components of the COP Updater are the following:

  • MQTT Subscription Manager: Manages the subscriptions needed in the MQTT broker by querying the Resource Catalogue (i.e. GOST).
  • MQTT Listener: receives and resolves incoming MQTT events.
  • COP Update: Updates the COP Database with information from MQTT.

The COP Updater is implemented as a Docker container with the actual software implementation made in .Net Core 2.0.

Go to Top