What the ISAAC PSIRT does
The ISAAC Product Security Incident Response Team (PSIRT) is the central point of contact for product cybersecurity matters affecting the ISAAC Platform and related products, services, and integrations.
Vulnerability and product security incident reports.
Technical validity, severity, exposure, and affected products.
Investigation, mitigation, remediation, and internal escalation.
Security advisories and customer notifications when appropriate.
If you believe you have identified a security vulnerability affecting an ISAAC product, service, or component, please contact the ISAAC PSIRT. No commercial relationship, support contract, or non-disclosure agreement is required to submit a report.
- For urgent matters, include “URGENT SECURITY ISSUE” in the subject line.
- For sensitive reports, encrypted communication is preferred.
ISAAC supports coordinated vulnerability disclosure. We ask reporters to allow reasonable time for investigation and remediation before publicly disclosing technical details that could place customers or systems at risk.
We aim to acknowledge receipt of new vulnerability reports within two business days.
We review the report, determine whether it affects an ISAAC product or service, and identify affected versions and configurations.
We evaluate severity, exploitability, customer exposure, operational impact, and applicable notification or reporting obligations.
When a vulnerability is confirmed, we coordinate remediation or mitigation, disclosure timing, and customer communication.
We document the resolution and publish a security advisory when public communication is appropriate.
The ISAAC PSIRT publishes security advisories for confirmed vulnerabilities when public communication is appropriate. Advisories may identify affected products and versions, severity, CVE identifiers, exploitation status, available mitigations, remediation instructions, and fixed versions.
No public ISAAC security advisories are listed.
Customers are encouraged to:
ISAAC supports good-faith security research conducted to improve product security. When performing research, please:
Good-faith commitment. ISAAC will not pursue legal action against researchers for good-faith security research conducted in accordance with this policy.
How we handle information submitted to ISAAC PSIRT
This notice explains how ISAAC collects, uses, protects, shares, and retains personal information in connection with vulnerability reporting and product security communications.
Version: 1.0
Effective date: [Month Day, Year]
Last updated: [Month Day, Year]
ISAAC respects the privacy of individuals who report security vulnerabilities, participate in coordinated vulnerability disclosure activities, or communicate with the ISAAC Product Security Incident Response Team (PSIRT).
This Privacy Notice explains how ISAAC PSIRT collects, uses, stores, protects, shares, and retains personal information received through product security activities, including vulnerability reporting, security investigations, coordinated disclosure, security advisories, and related communications.
This notice applies only to product-security-related processing. It should be read together with the ISAAC Vulnerability Disclosure Policy and any general ISAAC privacy policy that applies to the website or service through which information is submitted.
ISAAC operates the Product Security Incident Response Team responsible for receiving, assessing, investigating, coordinating, and responding to security vulnerabilities affecting ISAAC products and services.
For the processing described in this notice, the ISAAC legal entity identified below acts as the organisation responsible for determining why and how personal information is processed.
Legal entity: Smart Monkeys Inc.
Registered address:
10800 Biscayne Boulevard
Suite #400
Miami, FL 33161
Product security contact: security@isaacplatform.com
Privacy contact: privacy@isaacplatform.com
Depending on the report and the evidence supplied, ISAAC PSIRT may collect the following categories of information.
Reporter information
Vulnerability and investigation information
Communication records and technical metadata
Please avoid submitting unnecessary personal information, customer information, credentials, authentication tokens, private keys, or confidential business information. If sensitive information is inadvertently exposed, stop testing and notify ISAAC PSIRT promptly.
ISAAC PSIRT uses personal information received through product security activities for the following purposes:
1. Receive and assess
Receive, acknowledge, record, validate, triage, and investigate suspected vulnerabilities.
2. Protect and remediate
Assess severity and customer impact, coordinate mitigation or remediation, and protect ISAAC products, customers, and users.
3. Communicate and comply
Communicate with reporters, coordinate disclosure, publish advisories, preserve necessary records, and meet legal, regulatory, contractual, and audit obligations.
Where applicable law requires a legal basis, ISAAC PSIRT may rely on one or more of the following, depending on the circumstances and jurisdiction:
Where ISAAC PSIRT relies on legitimate interests, it will consider the necessity of the processing and its potential effect on the individuals concerned.
ISAAC PSIRT treats unpublicised vulnerability reports and associated personal information as sensitive information. ISAAC PSIRT applies technical and organisational measures designed to prevent unauthorised access, disclosure, alteration, loss, or misuse.
No method of transmission or storage can be guaranteed to be completely secure. Reporters should use ISAAC PSIRT encryption details published on the PSIRT page for sensitive submissions.
ISAAC PSIRT may share information only where reasonably necessary to investigate, remediate, coordinate disclosure, protect users, or comply with applicable obligations. Recipients may include:
ISAAC does not sell personal information submitted through vulnerability reports.
A public security advisory may describe the vulnerability, affected products and versions, severity, identifiers, exploitation status, mitigations, and available fixes. ISAAC PSIRT will not identify a reporter publicly without permission unless disclosure is required by law.
A reporter may choose to be acknowledged by name, credited under a pseudonym, or remain anonymous.
Product security investigations may involve personnel, suppliers, partners, customers, researchers, or authorities located in different countries. As a result, personal information may be transferred outside the country in which it was submitted.
Where personal information is transferred internationally, ISAAC applies appropriate contractual, organisational, and technical measures designed to protect personal information and comply with applicable privacy requirements.
ISAAC PSIRT retains personal information and vulnerability case records only for as long as reasonably necessary for the purposes described in this notice, subject to applicable legal, regulatory, contractual, security, audit, and evidence-preservation requirements.
Retention supports vulnerability investigation and remediation, coordinated disclosure, duplicate detection, product-security analysis, customer protection, compliance evidence, and responses to regulatory or legal enquiries.
Retention may be extended where a case remains active, litigation or an investigation is anticipated or ongoing, a legal hold applies, or continued retention is required to protect products and users.
Depending on your jurisdiction, you may have rights concerning your personal information, which may include:
These rights may be limited where processing is necessary to protect an investigation, preserve evidence, protect the rights of others, maintain product security, or comply with legal obligations. ISAAC PSIRT may need to verify your identity before responding to a request.
If you provide personal information about another person, submit only what is necessary for the security report and ensure that you are authorised to provide it. Do not include customer or end-user information unless it is essential to demonstrate the issue and cannot reasonably be removed or masked.
ISAAC may update this Privacy Notice to reflect changes in products, services, product-security practices, legal requirements, or organisational arrangements. The current version and its effective date will be published on the ISAAC Platform website.
ISAAC Privacy Contact
Email: privacy@isaacplatform.com
Product security reports: security@isaacplatform.com
Use the privacy contact for questions about this notice or requests concerning personal information processed through ISAAC product security activities. Use the product security contact to report suspected vulnerabilities and cybersecurity issues affecting ISAAC products or services.
For other matters, use the appropriate support, sales, or general contact channel on the ISAAC Platform website.
Help us keep ISAAC products secure
Report suspected vulnerabilities affecting the ISAAC Platform, ISAAC products, services, and integrations.
Version: 1.0
Effective date: [Month Day, Year]
Last updated: [Month Day, Year]
ISAAC is committed to maintaining the security of the ISAAC Platform and protecting the organisations that rely on it.
We recognise the valuable role that customers, security researchers, partners, integrators, and other members of the security community play in identifying potential vulnerabilities. This Vulnerability Disclosure Policy explains how to report a suspected vulnerability, what information to include, how ISAAC handles reports, and the conditions under which security research is considered to have been conducted in good faith.
By submitting a report, you help us investigate and address potential security issues before they can adversely affect ISAAC customers.
This policy applies to suspected vulnerabilities affecting the following, where developed, supplied, or operated by ISAAC:
A report may also concern a third-party component incorporated into or distributed with an ISAAC product. In such cases, ISAAC may coordinate with the relevant supplier, maintainer, or vulnerability coordination authority.
Out of scope
The following activities are not authorised under this policy:
If you are uncertain whether a product, service, or proposed research activity is in scope, contact the ISAAC Product Security Incident Response Team before proceeding.
Report suspected vulnerabilities to the ISAAC Product Security Incident Response Team.
Email: security@isaacplatform.com
For urgent matters, include URGENT SECURITY ISSUE in the subject line.
For a matter that may require immediate attention, include URGENT SECURITY ISSUE in the email subject.
For sensitive reports, encrypted communication is preferred. Use ISAAC PSIRT encryption details and public key on the PSIRT page.
No commercial relationship, support agreement, or non-disclosure agreement is required to submit a vulnerability report.
You may report anonymously. However, providing contact information allows ISAAC PSIRT to ask questions, share status information, and coordinate disclosure with you.
Please provide as much of the following information as is reasonably available:
Affected product
Vulnerability details
Disclosure information
Please do not include unnecessary personal information, customer information, credentials, private keys, or other secrets in the initial report.
When investigating a suspected vulnerability, please:
A vulnerability should not be exploited beyond the minimum extent necessary to establish its existence and potential impact.
ISAAC PSIRT supports coordinated vulnerability disclosure.
We ask reporters not to publicly disclose a suspected vulnerability before ISAAC PSIRT has had a reasonable opportunity to:
Disclosure timelines may vary according to the complexity of the issue, availability of mitigations, affected supply-chain components, customer impact, and evidence of active exploitation.
ISAAC will seek to discuss the proposed disclosure approach with the reporter. If circumstances require ISAAC PSIRT to delay publication, we will explain the reason where doing so does not expose confidential, legally protected, or security-sensitive information.
This policy does not require a reporter to agree to an indefinite disclosure restriction.
When you submit a vulnerability report, ISAAC PSIRT will endeavour to:
01. Acknowledge
Acknowledge the report within two business days.
02. Review
Assign the report, assess technical plausibility, and request additional information when required.
03. Coordinate
Coordinate remediation, mitigation, customer communication, and publication as appropriate.
The acknowledgement target is not a guarantee that the vulnerability will be validated or remediated within a specific period.
ISAAC PSIRT may close a report when it is determined to be:
Where practical, ISAAC PSIRT will explain the reason for closure.
ISAAC PSIRT treats unpublicised vulnerability reports as sensitive information.
We ask reporters to protect vulnerability information until a coordinated disclosure date has been agreed or ISAAC PSIRT has published an advisory.
ISAAC PSIRT may share report information with parties that have a legitimate need to participate in the investigation or remediation, including:
ISAAC will limit shared information to what is reasonably necessary for coordination, remediation, user protection, or compliance with applicable obligations.
ISAAC PSIRT supports good-faith security research conducted in accordance with this policy.
ISAAC PSIRT will not initiate legal action against a researcher solely for security research when the researcher:
If an activity is inconsistent with this policy, ISAAC PSIRT may request that it be stopped. Researchers are expected to comply promptly with such a request.
This policy does not:
ISAAC PSIRT appreciates the contributions of individuals and organisations that responsibly disclose vulnerabilities.
With the reporter’s permission, ISAAC PSIRT may acknowledge the reporter in:
A reporter may instead choose to remain anonymous.
ISAAC does not currently operate a public bug-bounty program.
Submission of a vulnerability report does not create an entitlement to payment, compensation, employment, a commercial relationship, or any other reward.
Any recognition or compensation offered by ISAAC PSIRT is discretionary and must be agreed in writing.
ISAAC PSIRT may publish a security advisory when a confirmed vulnerability requires communication to customers or the public.
An advisory may include:
ISAAC PSIRT may withhold technical details that would materially increase customer risk before an effective mitigation is broadly available.
Personal information submitted as part of a vulnerability report will be used to receive, investigate, coordinate, document, and respond to the report.
Reporters should provide only the personal information needed for these purposes. Where a reporter asks to remain anonymous, ISAAC PSIRT will respect that request except where disclosure is required by law.
Information associated with a report may be retained to:
Applicable privacy information should be referenced here before publication:
Privacy notice: ISAAC_PSIRT_Privacy_Notice
If a report concerns a third-party component used by an ISAAC product, ISAAC PSIRT may:
ISAAC PSIRT will not attribute a vulnerability to a third party publicly until the relevant information has been validated and disclosure has been appropriately coordinated.
ISAAC PSIRT may update this policy to reflect changes in its products, services, disclosure practices, or applicable requirements.
The current version and its effective date will be published on the ISAAC Platform website.
ISAAC Product Security Incident Response Team
Email: security@isaacplatform.com
Use this address for suspected vulnerabilities and cybersecurity issues affecting ISAAC products or services.
For product support, sales enquiries, or other non-security matters, use the appropriate contact channel on the ISAAC Platform website.