Timeline for Why is PDF still safe?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2015 at 13:23 | comment | added | Graham Hill | If you cannot tolerate or terminate, then you treat or transfer. You always end up doing one of the four. In this case most people will treat, for example with Rod's idea of a special machine (maybe a VM?) for opening these files. They could also transfer; go through an employment agency, for example, and have them open all the PDF files. | |
| May 5, 2015 at 13:09 | comment | added | Rod MacPherson | @arc-lupus This is precisely why security is done in layers. If, say you have an HR e-mail address that regularly gets PDFs from multiple unknown sources (resumes) it would be ideal to have the machine where those are viewed be more heavily restricted in what it can do on the network, and more closely monitored. If someone is planting malware in a PDF, they probably want to use it as a way to get into the network, or a way to cause havok on the network. If you limit what that computer can get to, you reduce the risk. | |
| May 5, 2015 at 12:50 | comment | added | arc_lupus | How do you handle pdfs from multiple sources, some which are potentially malicious, then, without knowing which are malicious, but you need the content of them? | |
| May 5, 2015 at 12:41 | history | answered | Graham Hill | CC BY-SA 3.0 |