Security

Prioritizing security: our commitment to safeguarding your information and privacy.

Magnet Forensics treats the security and privacy of our partners and customers with the highest importance. We work diligently to ensure that we’ve implemented and maintained proper security processes, standards, and procedures at all levels of our business.

This page is aimed at providing you with more information on our security infrastructure and practices. For more information on how we handle any data we collect, please refer to our Privacy Policy.

Product security

  • Secure software development practices – We follow industry best practices and the principles outlined in Microsoft SDL to ensure that security is incorporated into our software development processes from inception to deployment. Our software development adheres to secure coding practices, including threat modeling, code review, and testing, to prevent vulnerabilities from being introduced.
  • Regular vulnerability assessment and penetration testing – Products are regularly assessed for vulnerabilities through VAPT, ensuring they remain resilient against evolving threats.
  • Threat modeling – Exercises are conducted regularly to identify potential security vulnerabilities and mitigate them early in the development lifecycle.
  • Code review and testing – Rigorous review and testing includes static code analysis, dynamic application security testing, and manual code reviews to identify
    and address security flaws.
  • Security training and awareness – Development teams are regularly provided security training and awareness to ensure they are equipped with the necessary knowledge and skills to develop secure code.
  • Following principles and guidelines from the Open Web Application Security Project (OWASP) – Our development teams follow these best practices and guidelines to ensure that our software and web applications are built with security in mind–protecting against common web application vulnerabilities.
  • Vulnerability Disclosure Program – With this program, we accept, review, and address disclosed software vulnerabilities in a timely fashion.
  • Regular monitoring – In addition to monitoring, we also log and audit trust relationships used for authorization and access to any software development and build environments.
  • Multi-Factor Authentication – We enforce multi-factor authentication and conditional access across the environments relevant to developing and building software in a manner that minimizes security risk.

COMPLIANCE

  • Magnet Forensics holds the SOC 2 reports for following products:
    • Magnet Nexus 
    • Magnet One Hub 
    • Magnet Artifact IQ 
    • Magnet Review

Note: Please request the attestation documents and certification reports via your Sales Representative or support@magnetforensics.com.

Corporate Security

  • Access and authentication – Least privilege and multi-factor authentication enhance access control. Single sign-on (SSO) and Security Assertion Markup Language (SAML) streamline user authentication.
  • Network security – Network is fortified through vulnerability assessment, firewalls, and network segmentation.
  • Data security – We use encryption, third-party vetting, and prompt system updates to protect data against unauthorized access and vulnerabilities.
  • People security – We have mandatory awareness training and background checks, reducing insider threats and ensuring a secure environment.
  • Incident management – We continuously monitor infrastructure with managed detection and response (MDR) and log aggregation for swift threat detection and response.
  • Business Continuity (BCP) and Disaster Recovery (DR) – We have BCP/DR plans in place to ensure operational continuity and data recovery in the face of unexpected disruptions.

Responsible Disclosure

Magnet Forensics is committed to ensuring the safety and security of our customers. Toward this end, Magnet Forensics is sharing our policy for accepting vulnerability disclosures. We hope to foster an open partnership with the security community, and we recognize that the work the community does is important in continuing to ensure the safety and security of all our customers.

We have developed this policy to both reflect our corporate values and to uphold our legal responsibility to good-faith security researchers that are providing us with their expertise.

*Please note: Magnet Forensics does not operate a public bug bounty program and we make no offer of reward or compensation in exchange for submitting potential issues.

Program and Scope

Magnet Forensics accepts vulnerability disclosure submissions on all our products, tools, and platforms; however, we only commit to reviewing and reporting on submissions related to the most recent versions of the following products:

  • Magnet Atlas
  • Magnet Ignite
  • Magnet Axiom
  • Magnet Axiom cyber
  • Magnet Automate
  • Magnet Review
  • Magnet DVR Examiner
  • Magnet Witness
  • Magnet Outrider

Products and tools outside of the above list will be reviewed on a case-by-case basis with no promise of an outcome or report back to you. As our internal resources grow, we intend to increase the scope of applicable products and tools.

Restricted Testing

Certain test types are considered restricted under the Responsible Disclosure Program. Restricted vulnerabilities and activities include:

  • Physical testing
  • Social engineering
  • Phishing
  • Denial of service attacks
  • Resource exhaustion attacks
  • Any attempt to interrupt or degrade the services Magnet Forensics offers

*Researchers who submit a vulnerability disclosure to us will be recognized in our release notes once the submission has been accepted, validated, and resolved by our Product Security team.

Legal Posture

Magnet Forensics agrees not to pursue legal action against individuals for engagement in the following activities (“Acceptable Activities”):

  • Submission of vulnerability disclosure to Magnet Forensics in compliance with this policy.
  • Testing of systems/research without harming Magnet Forensics or its customers, if they have received consent from all parties involved.
  • Vulnerability testing in compliance with this policy.
While Performing Acceptable Activities, We Require That All Security Researchers:
  • Do not store, share, compromise, or destroy Magnet Forensics or customer data. If personally identifiable information (PII) is encountered, you should immediately halt your activity, purge related data from your system, and immediately contact Magnet Forensics. This step protects any potentially vulnerable data, and you.
  • Adhere to the laws of their local jurisdiction and the legal jurisdiction of Magnet Forensics. For example, violating laws that would only result in a claim by Magnet Forensics (and not a criminal claim) may be acceptable as Magnet Forensics is authorizing the activity (reverse engineering or circumventing protective measures) to improve its system.
  • Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.
Communication Mechanisms and Process

How to Submit a Vulnerability

To submit a vulnerability report to the Magnet Forensics Product Security team at  securityconnect@magnetforensics.com.

Our Response to Your Submission

What We Would Like to See From You

  • Clear and accurate written reports in English.
  • Reports that include proof‐of-concept code.
  • Reports that do not only include crash dumps or other automated tool output.
  • A summary including how you found the bug, the impact, and any potential remediation.
  • Any plans or intentions by you of public disclosure.

What You Can Expect From Us

  • Acknowledgment to your email (within five business days).
  • After an initial review, we will send you an expected timeline of remediation as well as possible issues or challenges that may extend it. Note that we will prioritize remediation of Magnet Forensics products identified as ‘in scope’ in the above section.
  • An open dialogue to discuss issues.
  • Notification when the vulnerability analysis has completed each stage of our review.
  • Recognition after the vulnerability has been validated and fixed.