Artificial Intelligence and Automation in Mobility Risk Management

1. ARTIFICIAL INTELLIGENCE AND
AUTOMATION IN MOBILITY RISK
MANAGEMENT

2. ▪ EXOP DEVELOPMENTS
▪ KEY QUESTION(S) FOR TRAVEL SECURITY MANAGERS
▪ CLASSICAL ALERTING APPROACH
▪ HOW CAN TECHNOLOGY SUPPORT ALERTING SYSTEMS?
▪ AUTOMATIC INCIDENT DETECTION
▪ LIVE DEMONSTRATION OF “TEXT ANALYTICS”
OUTLINE

3. DEVELOPMENTS
2007 - 2014 INTELLIGENCE PROVIDER FOR HIGH RISK COUNTRIES
ON-GROUND PROJECT ASSESSMENTS IN HIGH RISK COUNTRIES
24/7 INTELLIGENCE & COUNTRY RISK DATABASES
24/7 EMERGENCY HOTLINE FOR TRAVEL SECURITY / RISK AND STRATEGIC ANALYSIS
2015 – 2018 TRANSFORMATION INTO A DIGITAL COMPANY
RESEARCH ON ARTIFICIAL INTELLIGENCE
FINALIZING SAAS/DAAS TRAVEL SECURITY PRODUCT
REVOLUTION OF MOBILITY SECURITY MANAGEMENT

4. KEY QUESTION(S) FOR SECURITY MANAGERS

5. WHICH OF MY TRAVELERS HAVE BEEN AFFECTED BY A
SECURITY INCIDENT AND NEED HELP?
IMMEDIATE ∙ ANYTIME ∙ WORLDWIDE
KEY QUESTION(S) FOR SECURITY MANAGERS

6. CLASSICAL ALERTING APPROACH
2. INCIDENT SELECTION 3. MATCHING INCIDENT TO
TRAVELERS LOCATION
10 – 60 min
6. SENDING ALERTS7. STATUS CALLS TO
TRAVELERS
8. FINAL STATUS TO
MANAGER
4. SELECTING
STAKEHOLDERS
TRAVELER/MANAGER
9. INITIATE
EMERGENCY
PROCESS
5. WRITE THE REPORT
IN THE REQUIRED
LANGUAGE (IF POSSIBLE)
10 – 30 min
1 – 5 min
10 – 40 min10 – 120 min10 – 60 min
1. OSINT/SOCMINT
24/7 MONITORING
SLOW (~1 – 3 HOURS) ∙ NOT SCALABLE ∙ LIMITED LANGUAGES

7. HOW CAN
TECHNOLOGY
SUPPORT ALERTING
SYSTEMS?

8. HOW CAN TECHNOLOGY SUPPORT ALERTING SYSTEMS?
2. INCIDENT SELECTION 3. MATCHING INCIDENT TO
TRAVELERS LOCATION
10 – 60 min
6. SENDING ALERTS7. STATUS CALLS TO
TRAVELERS
8. FINAL STATUS TO
MANAGER
4. SELECTING
STAKEHOLDERS
TRAVELER/MANAGER
9. INITIATE
EMERGENCY
PROCESS
5. WRITE THE REPORT
IN THE REQUIRED
LANGUAGE (IF POSSIBLE)
10 – 30 min
1 – 5 min
10 – 40 min10 – 120 min10 – 60 min
1. OSINT/SOCMINT
24/7 MONITORING
INCIDENT DETECTION
MULTI-CHANNEL REPORTING

9. HOW CAN TECHNOLOGY SUPPORT ALERTING SYSTEM?
▪ IDENTIFY INCIDENTS AUTOMATICALLY, GLOBALLY AND IN REAL-TIME
▪ MATCH THE LOCATION OF THE TRAVELERS WITH SECURITY INCIDENTS IN SECONDS
▪ DYNAMIC ALARM/REPORTING CONFIGURATIONS BASED ON CLIENTS NEEDS
▪ ASK PROACTIVELY FOR THE STATUS OF THE POTENTIAL AFFECTED TRAVELERS
▪ COMMUNICATE WITH THE TRAVELERS AND MANAGERS IN THEIR LANGUAGES
▪ ALARM THE RESPONSIBLE MANAGEMENT IF SUPPORT IS NEEDED
▪ TRIGGER DEDICATED EMERGENCY SUPPORT MEASURES AUTOMATICALLY
INCIDENT DETECTOR WITH MULTI-CHANNEL ALARM AND REPORTING
AUTOMATIC (1 -5 MIN) ∙ SCALABLE ∙ MULTI-LINGUAL

10. AUTOMATIC INCIDENT DETECTION
MACHINE LEARNING AND NATURAL LANGUAGE PROCESSING
GLOBALLY AND IN REAL-TIME

11. AUTOMATIC INCIDENTS DETECTION
MULTILINGUAL
CLUSTERING
CATEGORIZATION
LOCATION
DETECTION
INFORMATION
EXTRACTION
LOCATION
DETECTION

12. AUTOMATIC INCIDENTS DETECTION
BIGDATA
VERIFICATION TO
ENSURE HIGH
ACCURACY
COLLECTION
SELECTIONANALYSIS
SECURITY INCIDENTS
THOUSANDS OF OSINT/SOCMINT
SOURCES IN MULTIPLE LANGUAGES
L
E
A
R
N
I
N
G

13. ▪ MULTIPLE LANGUAGES
ENGLISH, DEUTSCH, FRANÇAIS, ESPAÑOL, ITALIANO, ‫العربية‬, 中国, …
▪ OPEN DOMAIN
SECURITY-RELATED OR WHATEVER
▪ AMBIGUOUS
STAYS AT THE HILTON HOTEL IN PARIS
▪ CONTEXT DRIVEN
THERE ARE MORE THAN 50 IN THE WORLD
AUTOMATIC INCIDENTS DETECTION
HOW TO HANDLE UNSTRUCTURE DATA?

14. AUTOMATIC INCIDENTS DETECTION
HOW DOES OUR A.I. TECHNOLOGY UNDERSTAND A SENTENCE?

15. AUTOMATIC INCIDENTS DETECTION
DATA
ACQUISITION
CONTENT
EXTRACTION
LINGUISTIC
ANALYSIS
GEOPARSING
TEXT
CLASSIFICATION
INCIDENTS

16. LIVE DEMONSTRATION OF “TEXT ANALYTICS”

17. SLOW ∙ NOT SCALABLE ∙ LIMITED LANGUAGES
TIME PERIOD: ~1 – 3 HOURS
3.
MATCHING
INCIDENTS TO
TRAVELER
LOCATION
1.
OSINT /SOCMINT
24/7
6.
SENDING ALERTS
4.
SELECTING STAKE HOLDERS
2.
INCIDENT SELECTION
5.
LANGUAGE SELECTION
7.
STATUS CALLS
TRAVELER FINAL STATUS
TO MANAGER
8.
INITIATING
EMERGENCY
PROCESS
TIME PERIOD 1-5 MINUTES
AUTOMATIC ∙ SCALABLE ∙ MULTI-LINGUAL
1-5 MIN.1.
OSINT /SOCMINT
24/7
8.
FINAL STATUS
TO MANAGER

18. EXOP GmbH
Info@exop-group.com
Matteo Grella
Head of Artificial Intelligence
www.exop-group.com