incident.io
Last updated by the developer on: July 15, 2024
General information
Information provided by Pineapple Technology Ltd to Microsoft:
| Information | Response |
|---|---|
| App name | incident.io |
| ID | WA200007219 |
| Office 365 clients supported | Microsoft Teams |
| Partner company name | Pineapple Technology Ltd |
| Company's website | https://incident.io |
| App's Terms of Use | https://incident.io/terms |
| Core functionality of the app | Manage incidents at scale, without leaving Microsoft Teams. With a beautifully simple interface and powerful workflow automation, incident.io ensures entire organizations can seamlessly collaborate and manage incidents using Microsoft Teams for communication. |
| Company headquarter location | United Kingdom of Great Britain and Northern Ireland (the) |
| App info page | |
| What is the hosting environment or service model used to run your app? | Iaas |
| Which hosting cloud providers does the app use? | GCP |
| Customer support contact. | [email protected] |
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 Pineapple Technology Ltd 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? | Yes |
| What data is processed by your app? | Information on the users, teams and channels in the tenant, and channel messages within any Teams which the app is installed to |
| 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? | User, team and channel information. |
| If underlying infastructure processes or stores Microsoft customer data, where is this data geographically stored? | Belgium |
| Do you have an established data rentention and disposal process? | Yes |
| How long is data retained after account termination? | More than 90days |
| Do you have an established data access management process? | Yes |
| Do you transfer customer data or customer content to third parties or sub-processors? | Yes |
| Do you have data sharing agreements in place with any third party service you share Microsoft customer data with? | Yes |
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? | Yes |
| Does your environment use traditional anti-malware protection or application controls? | TraditionalAntiMalware, ApplicationControls |
| Do you have an established process for indentifying and risk ranking security vulnerabilities? | Yes |
| Do you have a policy that governs your service level agreement (SLA) for applying patches? | No |
| Do you carry out patch management activities according to your patching policy SLAs? | Yes |
| Does your enviroment have any unsupported operating systems or software? | No |
| Do you conduct quarterly vulnerability scanning on your app and the infastructure 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? | Yes |
| Multifactor Authentication (MFA) enabled for: | DNSManagement, CodeRepositories, Credential |
| 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? | Yes |
| 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 |
| When a security event is detected are alerts automatically sent to an employee for triage? | Yes |
| Do you have a formal information security risk management process established? | Yes |
| Do you have a formal security incident response process documented and established? | Yes |
| Do you report app or service data breaches to supervisory authorities and individuals affected by the breach within 72 hours of detection? | Yes |
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)? | 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 |
| Does the app comply with Service Organization Controls (SOC 2)? | Yes |
| Which SOC 2 certification did you achieve? | type2 |
| Most recent SOC2 certification date | 2024-03-09 |
| 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? | 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)? | N/A |
| Does the app comply with International Organization for Standardization (ISO 27002)? | N/A |
| 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 |
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)? | Yes |
| Does the app have an external-facing privacy notice that describes how it collects, uses, shares, and stores customer data? | Yes |
| Privacy Policy URL | https://incident.io/privacy |
| 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? | Yes |
| Does the app have capabilities to restrict or limit the processing of an individual's personal data upon request? | N/A |
| Does the app provide individuals the ability to correct or update their personal data? | N/A |
| 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 |
Questions
Questions or updates to any of the information you see here? Contact us!
| Information | Response |
|---|---|
| Does your application integrate with Microsoft identity platform (Microsoft Entra ID) 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? | 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 |
| 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 Microsoft Entra App ID Channel.Create.Group rsc Create a channel when an incident is declared, to co-ordinate response in 68ac5791-0672-47f9-a1e1-f2ef2b656f61 Channel.Delete.Group rsc Delete or archive incident channels once the incident has been resolved. 68ac5791-0672-47f9-a1e1-f2ef2b656f61 Channel.ReadBasic.All application Allow customers to configure workflows involving specific channels in their organisation, if necessary 68ac5791-0672-47f9-a1e1-f2ef2b656f61 ChannelMessage.Read.Group rsc Build analytics for customers based on activity in incident channels - for example how much time employees are spending responding to incidents 68ac5791-0672-47f9-a1e1-f2ef2b656f61 ChannelMessage.Send rsc Send messages to channels where the app is installed 68ac5791-0672-47f9-a1e1-f2ef2b656f61 ChannelSettings.ReadWrite.Group rsc Rename incident channels, to ensure the channel name reflects current information about the incident 68ac5791-0672-47f9-a1e1-f2ef2b656f61 Member.Read.Group rsc Offer different actions for users who are in the Team where incidents are handled vs those who are not in that team 68ac5791-0672-47f9-a1e1-f2ef2b656f61 OrganizationalBranding.Read.All application Show the customer organisation's name and logo within incident.io, so they understand 68ac5791-0672-47f9-a1e1-f2ef2b656f61 Owner.Read.Group rsc Know who can take owner-only actions within the Team where incidents are handled, such as installing a newer version of the app 68ac5791-0672-47f9-a1e1-f2ef2b656f61 Team.Create delegated Create a Team to run incidents in 68ac5791-0672-47f9-a1e1-f2ef2b656f61 Team.ReadBasic.All application Allow customers to configure workflows involving specific teams in their organisation, if required 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamMember.Read.Group rsc Offer different actions for users who are in the Team where incidents are handled vs those who are not in that team 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamSettings.Read.Group rsc Understand settings in the team where incidents are handled, to debug issues around who can take actions within that team 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamsAppInstallation.Read.Group rsc Check which version of the incident.io app is installed, to prompt for an upgrade when required 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamsAppInstallation.ReadWriteForUser.All application Install the Teams app to any user, in order to send them notifications via a Chat 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamsAppInstallation.ReadWriteSelfForTeam delegated Install the Teams app to the Incidents team created during the setup process 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamsTab.Create.Group rsc Create a tab in incident channels, where additional incident response actions can be taken 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamsTab.Read.Group rsc Manage the tab in incident channels, where additional incident response actions can be taken 68ac5791-0672-47f9-a1e1-f2ef2b656f61 TeamsTab.ReadWrite.Group rsc Manage the tab in incident channels, where additional incident response actions can be taken 68ac5791-0672-47f9-a1e1-f2ef2b656f61 User.ReadBasic.All application Allow customers to configure workflows that allow sending a message to any user in their organisation, if necessary 68ac5791-0672-47f9-a1e1-f2ef2b656f61 delegated Log the user in via Microsoft Entra single sign on, using their email address 68ac5791-0672-47f9-a1e1-f2ef2b656f61 openid delegated Log the user in via Microsoft Entra SSO 68ac5791-0672-47f9-a1e1-f2ef2b656f61 profile delegated Create a user in incident.io when signing in with Microsoft Entra, with their name 68ac5791-0672-47f9-a1e1-f2ef2b656f61
This application does not have Additional APIs.
Questions
Questions or updates to any of the information you see here? Contact us!