By Dana Pirvu<\/a>, Manager, Penetration Testing, Adobe<\/h2>\n\n\n\n\n\n<\/p>\n\n\n\n![\"Renae](\"https:\/\/miro.medium.com\/v2\/resize:fill:88:88\/1*_2c2rNBYDHH7262294wRcA.jpeg\")
<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/a><\/p>\n\n\n\n\n![\"Adobe](\"https:\/\/miro.medium.com\/v2\/resize:fill:48:48\/1*riyFijvwTfGcWNf1guRNtg.png\")
<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n![\"\"]()
<\/picture><\/div>\n<\/div>Generated with Adobe Firefly<\/a>.<\/figcaption><\/figure>\nAs adoption of generative AI (GenAI) continues to grow, adversarial interest in compromising the security posture of all applications and services \u2014 whether they leverage GenAI or not \u2014 is increasing as well. Companies that develop and deliver the complex software on which so much of the world\u2019s economy depends must focus their efforts on defending against these attacks.<\/p>\n
At Adobe, we believe the best way to measure the security posture of a product is by thinking like an adversary. That\u2019s why we\u2019ve incorporated this tenet into the foundation of the Adobe Security Testing Reports<\/a>, where we rigorously test each of our products from an adversary-aware perspective and measure them against proven, exploitable threats. The resulting product-specific reports provide a transparent view into the wide range of security testing Adobe conducts, which helps us build trust with our customers and partners. In this blog, I will explain how Adobe puts together our annual Security Testing Reports.<\/p>\nAdobe\u2019s annual security testing regime includes five (5) different types of tests:<\/p>\n
\n- Outsourced (or Third-Party) Penetration Testing: <\/strong>Bypassing user access control restrictions and\/or gaining privileged access to infrastructure through exploitation of applications and network-related vulnerabilities from an adversarial perspective, outsourced pen tests are externally facing from outside Adobe\u2019s network and provide an objective view of Adobe products\u2019 security posture.<\/li>\n
- Internal Penetration Testing:<\/strong> Employing manual testing techniques and automated tools to evaluate internal systems, applications, and networks, internal pen tests are performed in a staged environment inside Adobe\u2019s network and simulate real-world attacks to measure the effectiveness of existing security measures;<\/li>\n
- Red Team Testing:<\/strong> Challenging our security teams\u2019 cyber defenses using customized toolkits, Adobe Security\u2019s Red Team<\/a> employs offensive techniques to evaluate our preparedness to defend against various real-world adversaries;<\/li>\n
- Bug Bounty: <\/strong>Collaborating with a global community of external security researchers and ethical hackers helps Adobe provide an extra layer of protection to customers by finding and reporting undiscovered vulnerabilities to our product security teams before real-world adversaries can exploit them.<\/li>\n
- Customer Penetration Testing:<\/strong> In some exceptional circumstances, Adobe is able to accommodate customer-led penetration testing. Any findings uncovered from these tests provide an extra input to our security teams.<\/li>\n<\/ul>\n
Adobe Security Testing Reports<\/a> help achieve consistency in testing across our products, including those with GenAI features, by using the same methodologies, guidelines, industry standards, and best practices to test all products. Adobe then does not publish the results of the Security Testing Reports until all identified vulnerabilities have been addressed and either fixed or mitigated.<\/p>\nIn addition to the independent, third-party testing firm\u2019s attestation, each Adobe Security Testing Report also includes:<\/p>\n
\n- Testing Scope:<\/strong> Specifies the solution components included in the assessment.<\/li>\n
- Testing Approach:<\/strong> Outlines the methodology, guidelines, industry standards and best practices followed, including frameworks like the Open Worldwide Application Security Project (OWASP) Top 10 or the SysAdmin, Audit, Network, and Security (SANS) Top 25 to identify critical vulnerabilities.<\/li>\n
- Testing Methodology:<\/strong> Describes the assessment techniques and methodology followed, such as black-box testing or grey-box testing with source code review.<\/li>\n
- Test Results<\/strong>: Summarizes the vulnerabilities identified during the testing process.<\/li>\n
- Finding Summaries<\/strong>: Lists the exploitable vulnerabilities discovered during the assessment.<\/li>\n
- Finding Resolution<\/strong>: Provides the status of each identified vulnerability, such as whether it has been fixed or mitigated.<\/li>\n
- Finding Severity<\/strong>: Assigns a risk rating to each vulnerability based on CVSS 3.1 scoring.<\/li>\n
- Security Testing Categories<\/strong>: Details the defined policies, standards, and solutions, along with specific tests designed to achieve control adherence and resilience.<\/li>\n<\/ul>\n
Adobe views the Adobe Security Testing Reports as an ever-evolving source of customer trust, which is why we continuously work to improve both their content and transparency. One example of these improvements is the expansion of the outsourced pen testing component. Earlier this year, we expanded our testing methodology to include a hybrid testing approach, combining \u201cGrey Box\u201d as well as \u201cAuthenticated Black Box\u201d testing. Grey-box or source code-assisted tests involve sharing detailed information with testers, such as functionality documentation, user roles, and source code, to ensure a thorough assessment. In authenticated black-box testing, testers are provided with a full list of externally facing URLs\/domains and testing credentials to evaluate the application\u2019s security. This addition enables us to conduct comprehensive third-party testing that uses a hybrid testing methodology to verify both test coverage and completeness.<\/p>\n
We base our improvements for the Security Testing Reports not only on new threats and updated industry best practices, but also on feedback we receive directly from customers and stakeholders. In the most recent iteration, we incorporated customer-recommended features, including the severity rating and testing source for each finding, as well as a list of all testing sources included in the report.<\/p>\n
The Adobe Security Testing Reports are instrumental in helping our customers meet their own internal compliance and regulatory efforts. We often receive feedback that these reports have been valuable supplementary documentation that help customers assess Adobe\u2019s offerings against their own security requirements for application and network testing. Those customers operating in highly regulated industries have been at the forefront of this feedback as a beneficiary of Adobe\u2019s investment in developing comprehensive testing reports alongside other formal certifications found in the Adobe Trust Center<\/a>.<\/p>\nMore importantly, the Adobe Security Testing Reports also play a crucial role in providing our customers with enhanced visibility into our testing capabilities and the efforts we implement to ensure that our products are as resilient and secure as possible against adversarial attacks. We believe that providing this level of transparency enhances the trust our customers place in us, and we will continue to refine and expand these efforts to uphold our commitment to create safer digital experiences for all.<\/p>\n<\/div>\n
<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/a><\/p>\n <\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n As adoption of generative AI (GenAI) continues to grow, adversarial interest in compromising the security posture of all applications and services \u2014 whether they leverage GenAI or not \u2014 is increasing as well. Companies that develop and deliver the complex software on which so much of the world\u2019s economy depends must focus their efforts on defending against these attacks.<\/p>\n At Adobe, we believe the best way to measure the security posture of a product is by thinking like an adversary. That\u2019s why we\u2019ve incorporated this tenet into the foundation of the Adobe Security Testing Reports<\/a>, where we rigorously test each of our products from an adversary-aware perspective and measure them against proven, exploitable threats. The resulting product-specific reports provide a transparent view into the wide range of security testing Adobe conducts, which helps us build trust with our customers and partners. In this blog, I will explain how Adobe puts together our annual Security Testing Reports.<\/p>\n Adobe\u2019s annual security testing regime includes five (5) different types of tests:<\/p>\n Adobe Security Testing Reports<\/a> help achieve consistency in testing across our products, including those with GenAI features, by using the same methodologies, guidelines, industry standards, and best practices to test all products. Adobe then does not publish the results of the Security Testing Reports until all identified vulnerabilities have been addressed and either fixed or mitigated.<\/p>\n In addition to the independent, third-party testing firm\u2019s attestation, each Adobe Security Testing Report also includes:<\/p>\n Adobe views the Adobe Security Testing Reports as an ever-evolving source of customer trust, which is why we continuously work to improve both their content and transparency. One example of these improvements is the expansion of the outsourced pen testing component. Earlier this year, we expanded our testing methodology to include a hybrid testing approach, combining \u201cGrey Box\u201d as well as \u201cAuthenticated Black Box\u201d testing. Grey-box or source code-assisted tests involve sharing detailed information with testers, such as functionality documentation, user roles, and source code, to ensure a thorough assessment. In authenticated black-box testing, testers are provided with a full list of externally facing URLs\/domains and testing credentials to evaluate the application\u2019s security. This addition enables us to conduct comprehensive third-party testing that uses a hybrid testing methodology to verify both test coverage and completeness.<\/p>\n We base our improvements for the Security Testing Reports not only on new threats and updated industry best practices, but also on feedback we receive directly from customers and stakeholders. In the most recent iteration, we incorporated customer-recommended features, including the severity rating and testing source for each finding, as well as a list of all testing sources included in the report.<\/p>\n The Adobe Security Testing Reports are instrumental in helping our customers meet their own internal compliance and regulatory efforts. We often receive feedback that these reports have been valuable supplementary documentation that help customers assess Adobe\u2019s offerings against their own security requirements for application and network testing. Those customers operating in highly regulated industries have been at the forefront of this feedback as a beneficiary of Adobe\u2019s investment in developing comprehensive testing reports alongside other formal certifications found in the Adobe Trust Center<\/a>.<\/p>\n More importantly, the Adobe Security Testing Reports also play a crucial role in providing our customers with enhanced visibility into our testing capabilities and the efforts we implement to ensure that our products are as resilient and secure as possible against adversarial attacks. We believe that providing this level of transparency enhances the trust our customers place in us, and we will continue to refine and expand these efforts to uphold our commitment to create safer digital experiences for all.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n![\"\"](\"https:\/\/miro.medium.com\/v2\/resize:fit:640\/format:webp\/1*YPSwB6aTifed0IM1JBuTXg.jpeg)
\n
\n