Reports of 'radicalised' Canada airport staff spark concerns

Security clearances of four workers revoked after they were caught viewing radical material online


Afp March 30, 2017
PHOTO: AFP

MONTREAL, CANADA: The Canadian government said on Wednesday that it would take steps to counter any potential threats following a report saying workers at Montreal's airport had been 'radicalised'.

"The security and safety of all Canadians in airports and elsewhere remains a priority for this government. And we'll continue to work with all partners to ensure that our airports remain secure," said Canadian Prime Minister Justin Trudeau.

Muslim student in Canada barred from exam after refusing to remove hijab

According to the Journal de Montreal newspaper, at least four workers at the Montreal international airport had their security clearances revoked after showing suspicious signs. The workers had, reportedly, viewed online propaganda for the Islamic State (IS) group and visited websites that describe how to make a bomb.

Opposition Conservative MP, Tony Clement, called the reports 'troubling' and called for an immediate investigation. He also called for security to be stepped up while reiterating "the need to be ever vigilant against the threat of terrorism."

Parents feared Canadian teen could carry out terror attack - prosecutor

Transport Minister Marc Garneau assured that the government "takes security matters very seriously and will not hesitate to take appropriate action to mitigate risks and respond to any threats, when identified, to the transportation system."

He added that workers in the transport sector with security clearances are subject to continuous vetting and their access to restricted areas is "verified daily in a police database."

He noted that over 1,100 Canadian airport workers have been refused or have had their clearance revoked for one reason or another over the past two years.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ