Security & Responsible Disclosure

Our Commitment

At OMNISOC, security is at the core of everything we do. We are committed to protecting the integrity and confidentiality of our platform and our partners' data. We value the work of security researchers who help us maintain the highest standards.

This page is for security researchers who notice a potential issue on this website, as well as partners and customers who want to know where to send a security concern. It describes a way to report a possible vulnerability in the public website and its visitor-facing functions. It is not a list of guarantees about response times, a certification statement, or an invitation to test systems beyond this website.

Reporting a Vulnerability

If you believe you have identified a security vulnerability related to OMNISOC, please report it to partner@omni-soc.com. We encourage responsible disclosure and will review all submissions in good faith.

Email the security contact rather than putting the details in a public post or a general sales inquiry. Start with the page or feature affected, what you observed, and why you think it may be a security issue. If you can reproduce it, describe the steps in order and the result you expected compared with what happened. Include the date and approximate time you observed it, the browser or device involved if relevant, and any error message that helps explain the behavior. A concise report gives the team a clearer starting point for investigating the issue.

Guidelines

• Provide sufficient detail to reproduce the vulnerability.
• Allow reasonable time for us to investigate and remediate before public disclosure.
• Do not access, modify, or delete data belonging to other users or partners.
• Do not perform denial-of-service attacks or social engineering.
• Act in good faith and within the scope of this policy.

For this page, the relevant scope is the OMNI-SOC website: its public pages and visitor-facing features, including the inquiry form. A report about a broken link or a question about a service is different from a security vulnerability; use the contact details on the site for general questions. If a report involves sensitive information, avoid including another person's data in the email or continuing to access it. Describe the issue without sending passwords, private records, or other unnecessary personal information. The guidance above still applies if you encounter a problem while browsing on behalf of your organization.

What to Expect

We will acknowledge receipt of your report and keep you informed of the remediation progress. We may not operate a formal bug bounty program. Regardless, we are grateful for any responsible disclosures that help us improve our security posture.

After sending a report, you can use the same email thread to provide clarification or additional reproduction details. Please allow time for the issue to be investigated before public disclosure, as noted in the guidelines. The information you provide helps distinguish an isolated display problem from a security issue affecting a visitor-facing feature. This page explains the reporting channel; it does not specify a reward, a testing authorization outside the website, or a fixed investigation schedule.

If you are a partner or customer reporting something you encountered while using the site, explain whether it affected a public page, an inquiry you tried to send, or another visitor-facing interaction. A screenshot of the affected area can help when it does not reveal private information. If you are a researcher, keep any demonstration limited to the minimum needed to explain the problem and follow the restrictions above on other people's data. Reports with a clear location and reproducible observation are easier to review than a general warning without context.