Security Reporting
Security controls are calibrated to the evidence handled, the systems involved, and the client's authorized review boundary. This page describes current practices and the route for security questions; it does not expand an engagement's scope.
01 / Review point
Report suspected vulnerabilities affecting aibiosynergy.com by emailing info@aibiosynergy.com. Include the affected URL, a concise description, safe reproduction steps, and the potential impact.
Do not include credentials, private source code, personal health information, trade secrets, or sensitive organizational records in an initial report.
02 / Review point
Do not perform denial-of-service testing, social engineering, phishing, destructive testing, automated high-volume scanning, privacy invasion, or attempts to access data beyond the minimum needed to demonstrate a concern.
Stop testing and report promptly if you encounter personal data, credentials, confidential records, or evidence that continued testing could affect availability or integrity.
03 / Review point
This page covers the public AI Bio Synergy Inc website and its public inquiry forms. Reports about a public software repository must follow that repository's SECURITY.md policy. Commercial, licensing, partnership, and general project questions belong in the normal contact routes rather than the security channel.
04 / Review point
Reports are reviewed and routed according to the affected entity, service, or repository. We may request additional non-sensitive information, coordinate remediation with service providers, and confirm when a report is resolved or otherwise closed.
A report does not create a confidential relationship, contract, reward entitlement, or obligation to disclose private systems or records.
