Security
ObsidianWall takes the security of its technology and web properties seriously. If you believe you have identified a security vulnerability, please report it privately using the appropriate path below.
Report a Security Issue
For a suspected security vulnerability affecting obsidianwall.com, obsidianwall.dev, or another ObsidianWall-controlled system that does not have a more-specific security policy, contact:
Please include, where safely possible:
- the affected property, system, or component;
- a description of the suspected vulnerability and its potential impact;
- the relevant URL, environment, version, or other context;
- steps to reproduce the issue or a minimal proof of concept; and
- any suggested remediation you may have.
Please do not include passwords, authentication credentials, private keys, unnecessary personal information, confidential third-party information, or other unrelated sensitive data.
Do not submit suspected security vulnerabilities through the general ObsidianWall Contact form or a public issue tracker.
Verdict Security
Verdict maintains a dedicated security policy for vulnerabilities affecting the Verdict software, GitHub Action, and related product components.
That policy defines the applicable reporting process, supported versions, vulnerability scope, and other Verdict-specific security information.
Website and Corporate-System Security
Not every website issue is a security vulnerability.
For ordinary website issues, general questions, or other non-security matters, please use the Contact page. For suspected security vulnerabilities, use the private reporting process above.