*News from Adobes' Secure Software Engineering Team Blog: * Kyle Randolph, along with the security team for the Acrobat family of products, including Adobe Reader. This is the first post in a multi-part series about the new sandboxing technology used in the Adobe Reader Protected Mode feature that was announced back in July. We will take a technical tour of the sandbox architecture and look at how its different components operate and communicate in ways that will help contain malicious code execution.
*What is sandboxing?* A sandbox <http://en.wikipedia.org/wiki/Sandbox_%28computer_security%29> is a security mechanism used to run an application in a confined execution environment in which certain functions (such as installing or deleting files, or modifying system information) are prohibited. In Adobe Reader, “sandboxing” (also known as “Protected Mode”) adds an additional layer of defense by containing malicious code inside PDF files within the Adobe Reader sandbox and preventing elevated privilege execution on the user’s system. The Adobe Reader sandbox leverages the operating system’s security controls to constrain processes execution to the principle of least privilege<http://en.wikipedia.org/wiki/Principle_of_least_privilege> . For more information on this, visit below source URL: http://blogs.adobe.com/asset/2010/10/inside-adobe-reader-protected-mode-part-1-design.html Regards Sandeep Thakur -- You received this message because you are subscribed to the Google Groups "nforceit" group. To post to this group, send an email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nforceit?hl=en-GB.
