TCP 2

TCP 2 – Border management and surveillance

Lack of systematic identification and removal of illegal context on the internet

Capability Gap [2.CGF.14] Lack of systematic identification and removal of illegal context on the internet Background The practitioners had identified that they need technology solutions to assist them with the detection of illegal content in the web so they can remove it afterwards. This is described in Capability Gap Finding 2.CGF.14. Upon the identification of …

Lack of systematic identification and removal of illegal context on the internet Read More »

Lack in support of legacy / deployed solutions

Capability Gap [2.CGF.13] Lack in support of legacy / deployed solutions Background The practitioners indicated that they are using already a large number of technology solutions for border surveillance tasks. These technology solutions vary from surveillance cameras (at the beginning the installed base of cameras were deployed for daily observation and at a later stage …

Lack in support of legacy / deployed solutions Read More »

Lack of a multi-sectoral ecosystem for security solutions.

Capability Gap [2.CGF.12] Lack of a multi-sectoral ecosystem for security solutions. Background Security practitioners need solutions and products with open/common interconnection interfaces for systems that will be deployed in the borders. Further to Capability Gap No 2.CGF.11: Absence of security solution standardisation and certification, an approach is required to interconnect (with minimum effort) solutions from …

Lack of a multi-sectoral ecosystem for security solutions. Read More »

Absence of a security solution standardisation and certification

Capability Gap [2.CGF.11] Absence of security solution standardisation and certification Background Practitioners highlighted the lack of commonly accepted and used technology standards for the security solutions deployed. Currently the security solutions are standardised as stand-alone systems. Most of the security solutions are vendor specific and not standardised / certified for deployment and interworking with existing …

Absence of a security solution standardisation and certification Read More »