Incident Lake

Publisher Attestation: 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. Microsoft makes no guarantees regarding the accuracy of the information.

Last updated by the developer on: August 13, 2026

General information

Information provided by 株式会社SIGQ to Microsoft:

Information Response
App name Incident Lake
ID WA200011687
Office 365 clients supported Microsoft Teams
Partner company name 株式会社SIGQ
Company's website https://company.sigq.io
App's Terms of Use https://incidentlake.com/terms
Core functionality of the app Incident Lake helps managers make faster, better incident decisions by unifying tool data with AI.
Company headquarter location Japan
App info page https://incidentlake.com
What is the hosting environment or service model used to run your app? Saas
Which hosting cloud providers does the app use? GCP, Aws
Is AI functionality part of the app�s core features or workflows? Yes

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 株式会社SIGQ 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? Incident-related communications
Does the app support TLS 1.2 or higher? Yes
Does the app or underlying infrastructure store any Microsoft customer data? Yes
What data is stored in your databases? Teams channel/thread messages and metadata (sender name, user ID, message ID, timestamps), Teams team/channel identifiers, and OAuth refresh tokens used to call Microsoft Graph on the customer’s behalf.
If underlying infastructure processes or stores Microsoft customer data, where is this data geographically stored? Japan
Do you have an established data rentention and disposal process? Yes
How long is data retained after account termination? Less than 30days
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!

This information has been provided by Incident Lake about the security practices this app employs.

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? Yes
Do you carry out patch management activities according to your patching policy SLAs? Yes
Does your enviroment have any unsupported operating systems or software? Yes
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: Credential, CodeRepositories, DNSManagement
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!

This information has been provided by Incident Lake regarding the compliance standards their app requires and has the certifications they have accomplished.

Information Response
Does the app comply with the Health Insurance Portability and Accounting Act (HIPAA)? No
Does the app comply with Health Information Trust Alliance, Common Security Framework (HITRUST CSF)? No
Has the organization achieved a Service Organization Controls (SOC 1) Certification? No
Has the organization achieved a Service Organization Controls (SOC 2) Certification? Yes
Which SOC 2 certification did you achieve? type1
Most recent SOC2 certification date 2025-12-12
Has the organization achieved a Service Organization Controls (SOC 3) Certification? No
Do you carry out annual PCI DSS assessments against the app and its supporting environment? No
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? No
Does the app comply with Family Educational Rights and Privacy Act (FERPA)? No
Does the app comply with Children's Online Privacy Protection Act (COPPA)? No
Does the app comply with Sarbanes-Oxley Act (SOX)? No
Does the app comply with NIST 800-171? No
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)? No

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? No
Does your app support Conditional Access policies? No
If your app does not use one of the above libraries, what authentication library or libraries does it use? We don't use MSAL or Microsoft Identity Web. Entra ID auth is implemented directly against the Microsoft identity platform v2.0 endpoints via standard HTTPS requests, using the OAuth 2.0 authorization code, refresh token, and client credentials grants. The Microsoft Teams bot uses the official Bot Framework SDK (botbuilder).
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.ReadBasic.All delegated Browse and select which channel to connect e7078863-1933-4b82-af1c-ba2369381d0b
ChannelMessage.Read.All delegated Read channel messages and fill conversation history into an incident record when a user run go/fill command e7078863-1933-4b82-af1c-ba2369381d0b
ChannelMessage.Send delegated Post generated incident postmortems back into the originating Teams channel / Thread e7078863-1933-4b82-af1c-ba2369381d0b
Files.ReadWrite.All delegated Upload generated postmortem document to SharePoint e7078863-1933-4b82-af1c-ba2369381d0b
Team.ReadBasic.All delegated Browse and select which Teams team to connect during setup e7078863-1933-4b82-af1c-ba2369381d0b
User.Read delegated Resolves the signed-in identity during the OAuth connection flow e7078863-1933-4b82-af1c-ba2369381d0b
User.Read.All delegated Matches Teams members to their corresponding SIGQ user accounts for member linking for task for incident and task reminder e7078863-1933-4b82-af1c-ba2369381d0b
offline_access delegated Maintain the connection between a Teams workspace and Incident Lake via silent token refresh, without repeatedly re-authenticate e7078863-1933-4b82-af1c-ba2369381d0b
openid delegated Required for standard OAuth setup flow e7078863-1933-4b82-af1c-ba2369381d0b
profile delegated Reads basic profile info (name) of the signed-in for display purposes e7078863-1933-4b82-af1c-ba2369381d0b

This application does not have Additional APIs.

Questions

Questions or updates to any of the information you see here? Contact us!

  • Last updated on