Adobe Acrobat Sign

Last updated by the developer on: February 23, 2023
General information
Information provided by Adobe to Microsoft:
Information | Response |
---|---|
App name | Adobe Acrobat Sign |
ID | WA104381233 |
Office 365 clients supported | Microsoft Teams |
Partner company name | Adobe |
Company's website | https://acrobat.adobe.com/us/en/sign.html |
App's Terms of Use | https://www.adobe.com/legal/terms.html |
Core functionality of the app | Streamline document-signing workflows and deliver amazing employee and customer experiences when you leverage Adobe Sign capabilities in Teams. You can sign documents, send them for legally binding e-signatures and approvals, and track their status — all with Adobe Sign for Teams, Microsoft's preferred e-sign solution. |
Company headquarter location | United States of America |
App info page | https://helpx.adobe.com/sign/help/adobesign_microsoft_teams... |
What is the hosting environment or service model used to run your app? | |
Which hosting cloud providers does the app use? | AWS, Azure |
Questions
Questions or updates to any of the information you see here? Contact us!
How the app handles data
This information has been provided by Adobe about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.
Information | Response |
---|---|
Does the app or underlying infrastructure process any data relating to a Microsoft customer or their device? | |
Does the app or underlying infrastructure store any Microsoft customer data? |
Questions
Questions or updates to any of the information you see here? Contact us!
Information from the Microsoft Cloud App Security catalog appears below.
Information | Response |
---|---|
Do you perform annual penetration testing on the app? | Yes |
Does the app have a documented disaster recovery plan, including a backup and restore strategy? | No |
Does your environment use traditional anti-malware protection or application controls? | |
Do you have an established process for indentifying and risk ranking security vulnerabilities? | |
Do you have a policy that governs your service level agreement (SLA) for applying patches? | |
Do you carry out patch management activities according to your patching policy SLAs? | |
Does your enviroment have any unsupported operating systems or software? | |
Do you conduct quarterly vulnerability scanning on your app and the infastructure that supports it? | |
Do you have a firewall installed on your external network boundary? | |
Do you have an established change management process used to review and approve change requests before they are deployed to production? | |
Is an additional person reviewing and approving all code change requests submitted to production by the original developer? | |
Do secure coding practices take into account common vulnerability classes such as OWASP Top 10? | |
Multifactor Authentication (MFA) enabled for: | |
Do you have an established process for provisioning, modification, and deletion of employee accounts? | |
Do you have Intrusion Detection and Prevention (IDPS) software deployed at the perimeter of the network boundary supporting your app? | |
Do you have event logging set up on all system components supporting your app? | |
When a security event is detected are alerts automatically sent to an employee for triage? | |
Do you have a formal information security risk management process established? | |
Do you have a formal security incident response process documented and established? |
Questions
Questions or updates to any of the information you see here? Contact us!
Information | Response |
---|---|
Does the app comply with the Health Insurance Portability and Accounting Act (HIPAA)? | Yes |
Does the app comply with Health Information Trust Alliance, Common Security Framework (HITRUST CSF)? | No |
Does the app comply with Service Organization Controls (SOC 1)? | No |
Does the app comply with Service Organization Controls (SOC 2)? | Yes |
Most recent SOC2 certification date | 2020-11-24 |
Does the app comply with Service Organization Controls (SOC 3)? | No |
Do you carry out annual PCI DSS assessments against the appand its supporting environment? | Yes |
Is the app International Organization for Standardization (ISO 27001) certified? | Yes |
Does the app comply with International Organization for Standardization (ISO 27018)? | No |
Does the app comply with International Organization for Standardization (ISO 27017)? | No |
Does the app comply with International Organization for Standardization (ISO 27002)? | No |
Is the app Federal Risk and Authorization Management Program (FedRAMP) compliant? | Yes |
Does the app comply with Family Educational Rights and Privacy Act (FERPA)? | Yes |
Does the app comply with Children's Online Privacy Protection Act (COPPA)? | No |
Does the app comply with Sarbanes-Oxley Act (SOX)? | N/A |
Does the app comply with NIST 800-171? | |
Has the app been Cloud Security Alliance (CSA Star) certified? | No |
Questions
Questions or updates to any of the information you see here? Contact us!
Information | Response |
---|---|
Do you have GDPR or other privacy or data protection requirements or obligations (such as CCPA)? |
Questions
Questions or updates to any of the information you see here? Contact us!
Information | Response |
---|---|
Does your application integrate with Microsoft Identity Platform (Azure AD) for single-sign on, API access, etc.? | Yes |
Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? | Yes |
Does your app use the latest version of MSAL (Microsoft Authentication Library) or Microsoft Identity Web for authentication? | false |
Does your app support Conditional Access policies? | No |
Does your app support Continuous Access Evaluation (CAE) | |
Does your app store any credentials in code? | |
Apps and add-ins for Microsoft 365 might use additional Microsoft APIs outside of Microsoft Graph. Does your app or add-in use additional Microsoft APIs? | Yes |
Data access using Microsoft Graph
Graph Permission Permission Type Justification Azure AD App ID Mail.ReadWrite delegated To populate the attached document, sender and receiver emails, and message content from emails to Adobe sign to send for signature. This is to save the user time to retype those fields in Adobe Sign. After an agreement is signed, we automatically compose a new email for the user to send an email to inform to his recipients that the transaction is done. a9b0c190-bafb-49ca-a61a-dab99cf2c43b People.Read delegated To autofill email address in the "Send for signature" experience, by typing some initial letters, do not require users to type the whole emails. a9b0c190-bafb-49ca-a61a-dab99cf2c43b User.Read delegated To read the profile of user and match their profile (basically, their email and userId) to our database so they can use Adobe Sign. a9b0c190-bafb-49ca-a61a-dab99cf2c43b offline_access delegated To refresh access token, when the current one is expired. For example, when user is in a "send for signature" window and leave it inactive for too long, we need to refresh a new token to keep the user active a9b0c190-bafb-49ca-a61a-dab99cf2c43b openid delegated Email and UserId. To sign user in to ensure their consent for the permission of using Adobe Sign app. a9b0c190-bafb-49ca-a61a-dab99cf2c43b
This application does not have Additional APIs.
Questions
Questions or updates to any of the information you see here? Contact us!