Application Security Overview - Adobe 12001196 - Acrobat - Mac Manual

Application Security Guide

1 Application Security Overview

This Application Security Guide describes configuration details for the Acrobat family of products,
including sandboxing (Protected View and Protected Mode), enhanced security, scripting controls,
attachments, and other features. The primary goal here is to encourage enterprise stakeholders who
configure and deploy clients to manage them in a secure way. This content is designed for IT
administrators, workflow owners, and technically savvy users who need to customize their application's
security capabilities.
Adobe provides a security model designed to help you protect your environment from security attacks.
You should explore the options for tuning applications for the desired security level. The big picture is
relatively simple: Acrobat products allow you to apply application-wide protections and disable risky
features while at the same time allowing you to selectively assign trust to files, folders, hosts, protocols,
apis, and other workflow components.
Note
The easiest way to propagate settings across your organization is to configure an installed application
and then use the Customization Wizard's registry feature to copy the settings to the application
installer.
Best practice checklist
Protect your systems and users
1. Enable Protected Mode.
2. Enable Protected View.
3. Enable Enhanced Security.
4. Review the JavaScript controls and set as needed.
5. Review the attachment white and black lists.
6. Review multimedia restrictions.
7. Review settings for XObjects, 3D content, and Flash.
Assign trust to workflow components
1. Set up privileged locations for files, folders, and hosts.
2. Use Trust Manager to configure internet access if you need more control than that offered by
Privileged Locations.
3. Set up cross domain access if you need it.
4. For digital signature workflows, set certificate trust and control user interaction with signed PDFs via
certificates, seed values, etc.
Many HKCU settings have an HKLM mirror so that IT can disable, lock, and control permissions in a way
that prevents end user changes.
Additional resources
Core Documentation
Resource
Section 1 Application Security Overview
Section 1 Application Security Overview
Description
Page 1