In the journey of developing SafeHorizon we have already achieved significant milestones. KEMEA collaborated closely with the project’s coordinator, technical partners, and Law Enforcement Agencies (LEAs) to define and analyse four distinct use case scenarios, i.e., monitoring transnational crime networks; criminal marketplace analysis; child sexual abuse and trafficking; malware-as-a-service (MaaS). Each end-user partner provided detailed scenarios based on their experience and operational needs. These scenarios outlined how SafeHorizon can assist LEAs in modeling and correlating criminals, actions, methods, and networks, covering areas such as monitoring, correlation, investigation, and prediction.

Then, the partners focused on gathering invaluable feedback from end-users regarding the functional and non-functional requirements of the system. This feedback was crucial for drafting the Concept of Operations (CONOPS) and creating a MoSCoW (Must have, Should have, Could have, and Won’t have but would like) list of user requirements. The MoSCoW list will continue to guide activities throughout the duration of the project and will be updated as needed.

For good measure, the characteristic use case scenarios along with the key LEAs’ requirements shall guide the design and development of the SafeHorizon modules, which will be presented in a separate blog post.

Looking Ahead

The progress we’ve made so far is a testament to the dedication and collaborative efforts of all partners involved in the SafeHorizon project. We are excited to continue our work and achieve even greater milestones. Stay tuned for more updates on our innovative approach to security!

Written by The Center of Security Studies (KEMEA)