What are ways to make sure that malicious content isn't embedded into documents and .pdfs?
There are two possible ways to interpret your question. One: How do you ensure that documents you receive or use don't contain malicious content? And two: How do you prevent malicious content being added to your own documents? I'll cover both issues to ensure I answer your question.
The way to tackle the first problem of avoiding malicious content embedded into documents is to ensure that:
- Your operating systems and all applications are kept up to date with the latest patches.
- Antivirus, antispyware and firewall applications are installed, up to date, and running.
- Documents are always scanned before being opened and users never open documents or links received unexpectedly or from unknown sources.
- Some form of antiphishing service is installed on the network.
The first three recommendations are pretty much standard security practice. Many attacks use newly discovered vulnerabilities, like the recent Adobe Flash player vulnerability, to embed and execute malware within a document. Therefore, keeping systems patched and keeping malware tools up to date with the latest signatures will greatly reduce the chances of such attacks being able to successfully infect your machine. Documents should always be scanned before being opened, and the settings on applications such as Word and Excel should prevent any macros embedded in a document from running without your explicit consent.
Your fourth layer of defense is not so widely used, but is becoming essential. Zero-day attacks can be lethal until vendors and AV products release patches or signature updates for their products. In order for hackers to launch such attacks, they need to entice victims to visit a particular website, which they try to do using phishing techniques, such as sending emails with enticing offers that link to their malicious site. An antiphishing service, such as that provided free by OpenDNS, blocks access to sites that are suspected of being malicious. This protection also helps safeguard those users who still insist on clicking on links from unknown or untrusted sources.
Problem two, how to secure a .pdf file or document from being infected with malware, requires a data and document lifecycle management system to protect documents at rest, in transit and when being accessed, shared or published. Besides encrypting and enforcing strict access controls, you should also aim where possible to have security reside within a document, to protect it as it moves through its lifecycle inside and outside the organization. Probably the most common way of achieving this protection is by using Adobe PDF files. PDFs include built-in controls to limit who can open and print them and how long recipients can access them. The files can also contain tracking to show who received them and if the files were opened.
Even if you use a rights management scheme, you are possibly open to other malware attack vectors if you share documents via a website that runs third-party ads or allows user input. Hackers can use cross-site scripting attacks to inject malicious code directly into your webpages if the site doesn't thoroughly validate user-generated input, received, for example, via a comments form.
Hackers are also using ads displayed on genuine sites as a way to inject malicious content or direct users to a malicious website. The Google Adwords service, for example, has been used to serve text ads that infect vulnerable Web surfers by routing them through an intermediate, malicious site. If you don't need to serve ads or show other third-party content on your site, then don't; you can immediately remove this attack vector.
Dig Deeper on Productivity apps and messaging security
Related Q&A from Michael Cobb
WhatsApp vulnerabilities can enable hackers to bypass end-to-end encryption and spoof messages. Expert Michael Cobb explains how these attacks work ... Continue Reading
Disabling Google location tracking involves more than turning off Location History. Learn how to manage your account settings to stop tracking ... Continue Reading
Compared to TLS 1.2, TLS 1.3 saw improvements in security, performance and privacy. Learn how TLS 1.3 eliminated vulnerabilities using cryptographic ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.