Product Security Incident Response Team

Our mission is to receive, assess, investigate, and coordinate the remediation of reported vulnerabilities and security issues in a responsible and transparent manner. We collaborate with customers, security researchers, partners, integrators, and industry stakeholders to strengthen the security posture of ISAAC products.

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.

Receive

Vulnerability and product security incident reports.

Assess

Technical validity, severity, exposure, and affected products.

Coordinate

Investigation, mitigation, remediation, and internal escalation.

Communicate

Security advisories and customer notifications when appropriate.

Report a vulnerability

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.

‍

Send an email to:
security@isaacplatform.com

- 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.

‍

Information to include

Reporter information

  • Name, or indicate that you prefer to remain anonymous
  • Organisation or affiliation, if applicable
  • Contact email address and optional telephone number

Vulnerability details

  • A concise title and description of the suspected vulnerability
  • Product name, version, deployment type, and affected component or interface
  • Steps to reproduce the issue in a controlled environment
  • Proof-of-concept code, screenshots, logs, traces, or other supporting evidence
  • Observed impact, security consequences, and any known workaround or mitigation

Disclosure information

  • Whether the issue has already been publicly disclosed
  • Whether a CVE identifier has been requested or assigned
  • Any intended or planned disclosure timeline

‍

What you can expect

1. Acknowledge

We aim to acknowledge receipt of new vulnerability reports within two business days.

2. Validate

We review the report, determine whether it affects an ISAAC product or service, and identify affected versions and configurations.

3. Assess

‍We evaluate severity, exploitability, customer exposure, operational impact, and applicable notification or reporting obligations.

4. Coordinate

When a vulnerability is confirmed, we coordinate remediation or mitigation, disclosure timing, and customer communication.

5. Close and publish

We document the resolution and publish a security advisory when public communication is appropriate.

‍

Security advisories

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.

Current Advisories

No public ISAAC security advisories are listed.

Product security updates

Customers are encouraged to:

  • Keep ISAAC products updated with the latest supported releases.
  • Review published security advisories and product release information.
  • Follow applicable deployment, hardening, and mitigation guidance.
  • Subscribe to security notifications when the service becomes available.

‍

Safe harbour for good-faith research

ISAAC supports good-faith security research conducted to improve product security. When performing research, please:

  • Avoid actions that could disrupt customer operations, availability, or safety.
  • Do not access, modify, copy, or retain customer data.
  • Do not use social engineering, physical attacks, denial-of-service testing, or destructive techniques.
  • Use systems and environments that you own or are explicitly authorised to test.
  • Report discovered vulnerabilities promptly through the published security contact.
  • Protect vulnerability details until a coordinated disclosure date is agreed.

‍

Good-faith commitment. ISAAC will not pursue legal action against researchers for good-faith security research conducted in accordance with this policy.

Privacy Notice


ISAAC Privacy Notice for Vulnerability Reporting

Privacy Notice

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]

1. Introduction

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.

2. Who we are

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.

Organisation details

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

3. Information we collect

Depending on the report and the evidence supplied, ISAAC PSIRT may collect the following categories of information.

Reporter information

  • Name and preferred form of identification
  • Organisation, company affiliation, and job title
  • Email address and optional telephone number
  • Public PGP key
  • Communication, acknowledgement, and disclosure preferences

Vulnerability and investigation information

  • Affected product, version, configuration, and environment information
  • Technical descriptions, reproduction steps, and proof-of-concept material
  • Screenshots, diagnostic files, logs, network captures, and system information
  • Security observations, potential impact, mitigations, and disclosure plans

Communication records and technical metadata

  • Email correspondence, case notes, investigation records, and disclosure coordination discussions
  • Message headers, submission timestamps, attachment metadata, and IP addresses contained in submitted evidence

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.

4. Why we use this information

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.

5. Legal bases for processing

Where applicable law requires a legal basis, ISAAC PSIRT may rely on one or more of the following, depending on the circumstances and jurisdiction:

  • ISAAC’s legitimate interests in maintaining product security, investigating reported vulnerabilities, preventing harm, and protecting customers and users
  • Compliance with legal or regulatory obligations, including product-security and incident-reporting obligations
  • The reporter’s consent where consent is specifically requested and is the appropriate basis
  • The establishment, exercise, or defence of legal claims
  • Performance of a contract where the processing is necessary for an applicable agreement with the reporter, customer, or partner

Where ISAAC PSIRT relies on legitimate interests, it will consider the necessity of the processing and its potential effect on the individuals concerned.

6. How we protect information

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.

  • Access restrictions based on role and business need
  • Authentication and access-control measures
  • Restricted security case records rather than investigation solely through email
  • Encryption during transmission and storage where appropriate
  • Security monitoring and audit logging
  • Confidentiality obligations and training for authorised personnel

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.

7. Who we may share information with

ISAAC PSIRT may share information only where reasonably necessary to investigate, remediate, coordinate disclosure, protect users, or comply with applicable obligations. Recipients may include:

  • Authorised ISAAC product development, support, security, legal, compliance, and management personnel
  • Component suppliers, technology partners, hosting providers, and specialist security advisers
  • Vulnerability coordination organisations and CVE Numbering Authorities
  • Governmental, regulatory, law-enforcement, or judicial authorities where required or permitted by law
  • Affected customers or users where communication is necessary for protection

ISAAC does not sell personal information submitted through vulnerability reports.

8. Public advisories and recognition

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.

9. International transfers

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.

10. Data retention

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.

11. Your privacy rights

Depending on your jurisdiction, you may have rights concerning your personal information, which may include:

  • Access to personal information held about you
  • Correction of inaccurate or incomplete information
  • Deletion of information in qualifying circumstances
  • Restriction of or objection to certain processing
  • Data portability where applicable
  • Withdrawal of consent where processing is based on consent
  • A complaint to the relevant privacy or data-protection authority

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.

12. Information about other people

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.

13. Changes to this notice

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.

14. Contact

Get in touch

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.

Vulnerability Disclosure Policy


ISAAC Vulnerability Disclosure Policy

Vulnerability disclosure

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]

1. Introduction

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.

2. Scope

This policy applies to suspected vulnerabilities affecting the following, where developed, supplied, or operated by ISAAC:

  • ISAAC Platform software
  • ISAAC hardware appliances
  • Embedded software and firmware supplied with ISAAC products
  • ISAAC-provided software and firmware update packages
  • ISAAC product interfaces and APIs
  • ISAAC-hosted services required for product functionality
  • Publicly accessible ISAAC websites and web applications

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:

  • Testing customer systems or production environments without the system owner’s explicit permission
  • Accessing or attempting to access another person’s account or data
  • Social engineering, phishing, or impersonation
  • Physical attacks against facilities, equipment, or personnel
  • Denial-of-service or resource-exhaustion testing
  • Destructive testing or actions that may impair the availability of a system
  • Installing malware, establishing persistence, or maintaining unauthorised access
  • Testing third-party products or services that are not controlled by ISAAC
  • Automated scanning that generates excessive traffic or affects service availability
  • Public disclosure of an unremediated vulnerability without attempting to coordinate with ISAAC Product Security Incident Response Team (PSIRT).

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.

3. Reporting a vulnerability

Report suspected vulnerabilities to the ISAAC Product Security Incident Response Team.

Security contact

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.

4. Information to include

Please provide as much of the following information as is reasonably available:

Affected product

  • Product or service name
  • Hardware model, if applicable
  • ISAAC Platform version
  • Firmware or operating-system image version
  • Affected module, interface, API, or dependency
  • Relevant configuration or deployment type

Vulnerability details

  • A concise description of the suspected vulnerability
  • The vulnerability category, if known
  • Steps required to reproduce the behaviour
  • Preconditions or privileges required
  • Proof-of-concept information
  • Screenshots, logs, network traces, or other supporting evidence
  • The actual or potential security impact
  • Any known mitigation or workaround

Disclosure information

  • Whether the vulnerability has already been disclosed to another party
  • Whether any information about it is already public
  • Whether a CVE identifier has been requested or assigned
  • Any intended publication or disclosure date

Please do not include unnecessary personal information, customer information, credentials, private keys, or other secrets in the initial report.

5. Research guidelines

When investigating a suspected vulnerability, please:

  • Test only systems that you own or are explicitly authorised to test.
  • Limit testing to what is necessary to confirm and document the vulnerability.
  • Take reasonable precautions to prevent privacy violations, data loss, and service disruption.
  • Stop testing if you access customer data, personal information, credentials, or confidential information.
  • Notify ISAAC PSIRT promptly if sensitive information is inadvertently accessed.
  • Do not download, copy, retain, modify, or disclose data that does not belong to you.
  • Delete any inadvertently obtained data as soon as ISAAC PSIRT confirms that it is no longer required to understand the report.
  • Do not use a vulnerability to obtain commercial advantage or demand payment.
  • Give ISAAC PSIRT a reasonable opportunity to investigate and address the issue before publishing technical details.
  • Comply with applicable laws and regulations.

A vulnerability should not be exploited beyond the minimum extent necessary to establish its existence and potential impact.

6. Coordinated disclosure

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:

  • Validate the report.
  • Determine affected products, versions, and configurations.
  • Assess severity and customer exposure.
  • Develop and test a remediation or mitigation.
  • Prepare customer guidance.
  • Complete any required coordination with suppliers, authorities, or vulnerability coordinators.

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.

7. What you can expect from ISAAC

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:

  • A duplicate of a previously reported issue
  • A non-security defect
  • Expected product behaviour
  • Not reproducible with the available information
  • Outside the scope of this policy
  • Associated with an unsupported or materially modified environment
  • Insufficiently supported after reasonable attempts to obtain additional information

Where practical, ISAAC PSIRT will explain the reason for closure.

8. Confidentiality

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:

  • Relevant ISAAC personnel
  • Component suppliers and technology partners
  • Vulnerability coordination organisations
  • CVE Numbering Authorities
  • Governmental or regulatory authorities
  • Affected customers, where communication is necessary for protection

ISAAC will limit shared information to what is reasonably necessary for coordination, remediation, user protection, or compliance with applicable obligations.

9. Safe harbour

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:

  • Makes a good-faith effort to comply with this policy
  • Tests only systems they own or are authorised to test
  • Avoids harm to ISAAC, its customers, users, partners, and third parties
  • Does not intentionally compromise privacy or access unnecessary data
  • Does not disrupt an ISAAC product or service
  • Reports the vulnerability promptly
  • Cooperates with reasonable requests related to validation and remediation
  • Complies with applicable law

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:

  • Authorise access to systems or data without the owner’s permission
  • Authorise conduct prohibited by law
  • Bind an independent third party
  • Provide immunity from actions taken by another organisation
  • Waive any rights that ISAAC may have concerning malicious, reckless, or harmful conduct

10. Recognition

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 published security advisory
  • Release documentation
  • A security acknowledgements page
  • Other coordinated communications

A reporter may instead choose to remain anonymous.

11. Vulnerability rewards

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.

12. Security advisories

ISAAC PSIRT may publish a security advisory when a confirmed vulnerability requires communication to customers or the public.

An advisory may include:

  • Advisory identifier
  • Publication and revision dates
  • Vulnerability description
  • Affected products and versions
  • Severity assessment
  • CVE identifier, where applicable
  • Known exploitation status
  • Mitigations and workarounds
  • Fixed or updated versions
  • Upgrade or remediation instructions
  • Reporter acknowledgement

ISAAC PSIRT may withhold technical details that would materially increase customer risk before an effective mitigation is broadly available.

13. Data protection

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:

  • Maintain the vulnerability case record
  • Document investigation and remediation decisions
  • Prevent duplicate investigations
  • Demonstrate compliance with applicable obligations
  • Support future product-security analysis

Applicable privacy information should be referenced here before publication:

Privacy notice: ISAAC_PSIRT_Privacy_Notice

14. Third-party vulnerabilities

If a report concerns a third-party component used by an ISAAC product, ISAAC PSIRT may:

  • Notify the relevant supplier or maintainer
  • Coordinate remediation and disclosure with that party
  • Refer the report to an appropriate vulnerability coordinator
  • Publish ISAAC-specific mitigation or impact information
  • Ask the reporter to coordinate with the component owner

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.

15. Policy changes

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.

16. Contact

Get in touch

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.