App Service Information
App Service Data Handling, Security, Compliance, Privacy & Identity information.
The information on this page is based on a self-assessment report provided by the app developer on the security, compliance, and data handling practices followed by this app.
Last update by the developer on: January 11, 2022 (Note: The below information is provided on a best effort basis and ongoing review.)
View in Teams Store: [search in Teams Apps]
View in App Source: web link
General
Application information.
Information | Response |
---|---|
App name | Contact Center |
ID | WA200001428 |
Microsoft 365 clients supported | Microsoft Teams |
Partner company name | Landis Technologies LLC |
URL of partner website | |
URL of Teams application info page | |
URL of Privacy Policy | |
URL of Terms of Use | |
Core functionality of the app | Contact center functionality for Microsoft Teams. |
Hosting environment | Microsoft Azure |
Service information
Information | Response |
---|---|
Category | Productivity |
Founded | 2018 |
Holding | Private |
Domain | cc.landis.cloud |
Domain registration | Microsoft Azure |
Logon URL | |
Cloud hosting provider(s) | Microsoft Azure |
Data type | none |
Headquarters | United States of America |
Data center | USA |
Data Handling
How the app handles data
This information has been provided by Landis Technologies LLC 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 Microsoft customer or their devices? | Yes |
What data is processed by your app? | calling data |
Does the app support TLS 1.1 or higher? | Yes |
Does the app or underlying infrastructure store any Microsoft customer data? | Yes |
What data is stored in your databases? | Call meta data details and call recordings. Information regarding users in the system, contact center configuration information. |
If underlying infrastructure processes or store Microsoft customer data, where is this data geographically stored? | US |
Do you have an established data retention and disposal process? | Yes |
How long is data retained after account termination? | -- |
Do you have an established data access management process? | Yes |
Do you transfer customer data or customer content to third parties or sub-processors? | No |
Aggregated statistics based on customer data | Yes |
Do you have data sharing agreements in place with any third party service you share Microsoft customer data with? | N/A |
Data access using Microsoft Graph
Yes. See Integration Permissions for more details.
Non-Microsoft services used
Yes. ReCaptcha.
Data access via bot
No
Telemetry data
Does any organizational identifiable information (OII) or end-user identifiable information (EUII) appear in this application's telemetry or logs? If yes, describe what data is stored and what are the retention and removal policies?
User name and UPN are stored as part of Microsoft Azure App Insight logging. This logging is retained by Azure App Insights for 90 days.
Human review of organizational information
No
Security
Security information below.
Information | Response |
---|---|
Do you perform annual penetration testing on the app? | No (at Microsoft Certification interval) |
Does the app have a documented disaster recovery plan, including a backup and restore strategy? | Yes |
Does your environment use traditional anti-malware protection or application controls? | Yes |
Do you have an established process for identifying and risk ranking security vulnerabilities? | Yes |
Do you have a policy that governs your service level agreement (SLA) for applying patches? | Yes |
Do you carry out patch management activities according to your patching policy SLAs? | Yes |
Does your environment have any unsupported operating systems or software? | No |
Do you conduct quarterly vulnerability scanning on your app and the infrastructure that supports it? | Yes |
Do you have a firewall installed on your external network boundary? | Yes |
Do you have an established change management process used to review and approve change requests before they are deployed to production? | Yes |
Is an additional person reviewing and approving all code change requests submitted to production by the original developer? | Yes |
Do secure coding practices take into account common vulnerability classes such as OWASP Top 10? | No |
Multifactor Authentication (MFA) enabled for: | CodeRepositories, DNSManagement, Credential and all items protected by Microsoft Azure Identity. |
Do you have an established process for provisioning, modification, and deletion of employee accounts? | Yes |
Do you have Intrusion Detection and Prevention (IDPS) software deployed at the perimeter of the network boundary supporting your app? | No |
Do you have event logging set up on all system components supporting your app? | Yes |
Are all logs reviewed on a regular cadence by human or automated tooling to detect potential security events? | Yes |
Do you have a formal information security risk management process established? | No |
Do you have a formal security incident response process documented and established? | |
Do you report app or service data breaches to supervisory authorities and individuals affected by the breach within 72 hours of detection? |
Security details
Item | Response |
---|---|
Latest breach | --- |
Data-at-rest encryption method | Transparent Data Encryption |
Multi-factor authentication | Yes, for system management. Available for all tenant users as well. |
IP address restriction | Yes, to some resources. |
Management portal user audit trail | Yes |
Management portal admin audit trail | Yes |
Data audit trail | |
User can upload data | Yes |
Data classification | |
Remember password | Login requires Microsoft Azure AD |
HTTP security headers | |
User-roles support | Yes |
File sharing | No |
Valid certificate name | Yes |
Trusted certificate | Yes |
Encryption protocol | TLS 1.2 |
Supports SAML | No |
Penetration Testing | Yes |
Requires user authentication | Yes |
Password policy | Yes |
Compliance
Compliance information to follow.
Information | Response |
---|---|
Does the app comply with the Health Insurance Portability and Accounting Act (HIPAA)? | N/A |
Does the app comply with Health Information Trust Alliance, Common Security Framework (HITRUST CSF)? | N/A |
Does the app comply with Service Organization Controls (SOC 1)? | N/A |
Most recent SOC1 certification date | |
Does the app comply with Service Organization Controls (SOC 2)? | No |
Which SOC 2 certification did you achieve? | |
Most recent SOC2 certification date | |
Does the app comply with Service Organization Controls (SOC 3)? | No |
Most recent SOC3 certification date | |
Do you carry out annual PCI DSS assessments against the app and its supporting environment? | N/A |
Is the app International Organization for Standardization (ISO 27001) certified? | No |
Does the app comply with International Organization for Standardization (ISO 27018)? | N/A |
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? | No |
Does the app comply with Family Educational Rights and Privacy Act (FERPA)? | N/A |
Does the app comply with Children's Online Privacy Protection Act (COPPA)? | N/A |
Does the app comply with Sarbanes-Oxley Act (SOX)? | N/A |
Does the app comply with NIST 800-171? | N/A |
Has the app been Cloud Security Alliance (CSA Star) certified? | No |
Privacy
Privacy information.
Information | Response |
---|---|
Do you have GDPR or other privacy or data protection requirements or obligations (such as CCPA)? | Yes. We are considered a Data Processor. |
Does the app have an external-facing privacy notice that describes how it collects, uses, shares, and stores customer data? | Yes |
Privacy Policy URL | |
Does the app perform automated decision making, including profiling that could have a legal effect or similar impact? | No |
Does the app process customer data for a secondary purpose not described in the privacy notice (i.e. marketing, analytics)? | No |
Do you process special categories of sensitive data (i.e. racial or ethnic origin, political opinion, religious or philosophical beliefs, genetic or biometric data, health data) or categories of data subject to breach notification laws? | No |
Does the app collect or process data from minors (i.e., individuals under the age of 16)? | No |
Does the app have capabilities to delete an individual's personal data upon request? | No |
Does the app have capabilities to restrict or limit the processing of an individual's personal data upon request? | No |
Does the app provide individuals the ability to correct or update their personal data? | Yes |
Are regular data security and privacy reviews performed (for example, Data Protection Impact Assessments or privacy risk assessments) to identify risks related to the processing of personal data for the app? | Yes |
Identity
Identity information. This information has been provided by Landis Technologies LLC about how this app handles authentication, authorization, application registration best practices, and other Identity criteria.
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? | |
Does your app use MSAL (Microsoft Authentication Library) for authentication? | Yes |
Does your app support Conditional Access policies? | No |
Does your app support Continuous Access Evaluation (CAE) | No |
Does your app store any credentials in code? | No |
Does your app request least privilege permissions for your scenario? | Yes |
Does your app's statically registered permissions accurately reflect the permissions your app will request dynamically and incrementally? | Yes |
Does your app support multi-tenancy? | Yes |
Does your app have a confidential client? | Yes |
Do you own all of the redirect Unified Resource Identifier (URI) registered for your app? | Yes |
For your app, what do you avoid using? | |
Does your app expose any web APIs? | Yes |
Does your permission model only allow calls to succeed if the client app receives the proper consent? | Yes |
Does your app use preview APIs? | Yes. When functionality not available otherwise. If the feature is in Preview it will be noted in release notes. |
Does your app use deprecated APIs? | No |
Last updated