Skip to main content

Responsible disclosure

How to report a security vulnerability in Oyoon Altaqnya's websites and systems.

1. Our commitment

Oyoon Altaqnya for Information Technology & Cybersecurity is committed to maintaining the security and integrity of its digital assets, websites and online services.

We recognize the valuable role that independent security researchers and the wider security community play in finding and responsibly reporting vulnerabilities. We welcome good-faith reports that help us identify, understand and address potential weaknesses in systems we own or operate.

2. Scope

This policy applies to security vulnerabilities found in digital assets that Oyoon Altaqnya owns or operates and has explicitly identified as in scope.

In scope:

  • otit.ly and its subdomains

Important: a publicly accessible system, domain, IP address or service is not, by itself, authorization to run security tests against it.

Customer environments, third-party systems, supplier infrastructure and other assets are excluded unless the relevant owner has given explicit written authorization.

3. How to report a vulnerability

If you find a potential vulnerability, report it to our security contact:

Security contact: security@otit.ly
Subject: Responsible Disclosure – [brief description of the vulnerability]

Reports in Arabic or English are welcome. Please include as much of the following as you can:

  • A clear description of the potential vulnerability.
  • The affected URL, system, application or asset.
  • The potential impact and a realistic exploitation scenario.
  • Steps to reproduce, and the minimum technical evidence needed to validate the issue.
  • Relevant screenshots, sanitized logs or proof-of-concept material, where appropriate.
  • Your preferred contact details, if you would like us to follow up.

Please do not include passwords, personal data, customer records, confidential business information or other sensitive information unless it is strictly necessary, and redact it wherever possible. Our contact details are also published in /.well-known/security.txt.

4. Researcher guidelines

When you research and report vulnerabilities, we ask that you:

  • Act in good faith and limit testing to the minimum needed to show that a vulnerability exists.
  • Avoid accessing, modifying, downloading or disclosing information that belongs to other people or organizations.
  • Do not disrupt services, degrade availability or run denial-of-service tests.
  • Do not use social engineering, phishing, physical intrusion or attacks against employees or customers.
  • Do not install persistent access, deploy malware or set up unauthorized command-and-control channels.
  • Do not run destructive tests, exfiltrate data or take actions that could compromise business operations.
  • Stop testing and report promptly if you meet sensitive information, or evidence that exploitation could affect other systems.
  • Keep the details confidential while we investigate and coordinate the fix.

Testing must stay within the authorized scope and comply with applicable laws and contractual obligations.

5. Our response process

When we receive a report, we will make reasonable efforts to:

  1. Acknowledge receipt within 3 working days.
  2. Validate the finding: assess the issue and ask for more information if needed.
  3. Assess the risk: determine the potential impact, severity and affected assets.
  4. Remediate or mitigate: act according to the risk and operational requirements.
  5. Communicate progress: give reasonable updates where we have your contact details.
  6. Close the report: tell you when the issue has been addressed, or when no actionable vulnerability was confirmed, where appropriate.

Response and fix timelines depend on the severity, complexity and operational impact of the issue.

6. Coordinated disclosure

Please give us a reasonable opportunity to investigate and fix a reported vulnerability before you publicly disclose technical details.

Any proposed public disclosure should be agreed with us in advance, with due regard to the progress of the fix, affected parties and the potential risk to users and customers. We aim to work constructively with researchers toward responsible disclosure.

7. Safe harbor

We will consider security research carried out in good faith and in line with this policy to be authorized within the scope defined here.

To the extent permitted by applicable law, we do not intend to start or recommend legal action against researchers solely for activities that comply with this policy.

This statement does not give permission to test third-party or customer systems, override contractual restrictions or authorize activities that the law prohibits. It does not prevent action in response to malicious conduct, out-of-scope testing, privacy violations or activities that create unacceptable risk.

8. Recognition

We appreciate the time and expertise that responsible researchers contribute. Where appropriate, and with the researcher’s consent, we may acknowledge contributors who help improve the security of our assets.

Recognition is discretionary. We do not offer financial rewards and do not guarantee public acknowledgment or other compensation unless we agree it in writing.

9. Out-of-scope activities

The following are not permitted under this policy:

  • Testing systems without authorization or outside the defined scope.
  • Denial-of-service, resource-exhaustion or destructive testing.
  • Unauthorized access to accounts, systems or confidential information.
  • Social engineering or attacks targeting employees, customers or suppliers.
  • Physical security testing or attempts to bypass physical access controls.
  • Exploitation that compromises third-party services or customer environments.
  • Public disclosure of exploitable details before coordinated disclosure.

Reports of suspected vulnerabilities are welcome; unauthorized exploitation is not.

10. Policy updates

We may revise this policy from time to time. The latest version published on this page applies to future reports and research, subject to applicable law.

11. Contact

For vulnerability reports and security-related communications:

Oyoon Altaqnya – Security Team
Website: https://otit.ly
Email: security@otit.ly

Please use this channel for vulnerability reports and privacy requests. For general inquiries, sales and support, use our regular contact channels.