Content Threat Removal

From Wikipedia, the free encyclopedia

Content Threat Removal (CTR) is a cyber security technology intended to defeat the threat posed by handling digital content in cyberspace.[1] Unlike other defences, including antivirus software and sandboxed execution, it does not rely on being able to detect threats. Similarly to Content Disarm and Reconstruction, CTR is designed to remove the threat without knowing whether it has done so, and acts without knowing if data contains a threat or not.

Detection strategies work by detecting unsafe content, and then blocking or removing that content. Content that is deemed safe is delivered to its destination. In contrast, Content Threat Removal assumes all data is hostile and delivers none of it to the destination, regardless of whether it is actually hostile. Although no data is delivered, the business information carried by the data is delivered, but using new data created for the purpose.

Threat[]

Advanced attacks continuously defeat defences that are based on detection. These are often referred to as zero day attacks, because as soon as they are discovered attack detection mechanisms must be updated to identify and neutralise the attack, and until they are, all systems are unprotected. These attacks succeed because attackers are skilled in finding new ways of evading detection. Polymorphic code can be used to evade the detection of known unsafe data and sandbox detection allows attacks to evade dynamic analysis.[2]

Method[]

A Content Threat Removal defence works by intercepting data on its way to its destination. The business information carried by the data is extracted and the data is discarded. Then entirely new, clean and safe data is built to carry the information to its destination.

The effect of building new data to carry the business information is that any unsafe elements of the original data are left behind and discarded. This includes executable data, macros, scripts and malformed data that triggers vulnerabilities in applications.

While CTR is a form of content transformation, not all transformations provide a complete defence against the content threat.[3]

Applicability[]

CTR is applicable to user-to-user traffic, such as email and chat, and machine-to-machine traffic, such as web services. Data transfers can be intercepted by in-line application layer proxies and these can transform the way information content is delivered to remove any threat.[4]

CTR works by extracting business information from data and it is not possible to extract information from executable code. This means CTR is not directly applicable to web browsing, since most web pages are code. It can, however, be applied to content that is downloaded from, and uploaded to, web sites.

Although most web pages cannot be transformed to render them safe, web browsing can be isolated and the remote access protocols used to reach the isolated environment can be subjected to CTR.

CTR provides a solution to the problem of Stegware.[5] It naturally removes detectable steganography and eliminates symbiotic and permutation steganography through normalisation.[6]

Availability[]

[7] have pioneered the development of CTR. A number of their products and services incorporate CTR, including application layer proxies for email and web services and ICAP (the Internet Content Adaptation Protocol) sidecar servers for uploaded and downloaded content.

Garrison provide a remote Desktop isolation solution where the display content is converted to a video signal that is then recoded as a video stream, using separate hardware chips.[8] This process removes any threat from the content of the display content.

See also[]

References[]

  1. ^ Wiseman, Simon (September 2017). "Content security through transformation". Computer Fraud and Security. Elsevier.
  2. ^ Keragala, Dilshan (January 2016). "Detecting Malware and Sandbox Evasion Techniques". SANS Institute.
  3. ^ Wiseman, Simon (May 2017). "Content Security through Transformation – Problem Statement". doi:10.13140/RG.2.2.13179.92969. Cite journal requires |journal= (help)
  4. ^ EP1721234A1, Graham Wyatt & Timothy Dean, "Threat mitigation in computer networks" 
  5. ^ Wiseman, Simon (December 2017). "Stegware – Using Steganography for Malicious Purposes". doi:10.13140/RG.2.2.15283.53289. Cite journal requires |journal= (help)
  6. ^ Wiseman, Simon (September 2017). "Defenders Guide to Steganography". doi:10.13140/RG.2.2.21608.98561. Cite journal requires |journal= (help)
  7. ^ "Content Threat Removal video".
  8. ^ "Silicon Assured Video Isolation".
Retrieved from ""