Report a security issue
Email ask@access.net.np with “Security report” in the subject. Include the affected domain or feature, an approximate timestamp, impact and the minimum steps needed to reproduce the issue.
Avoid sending live passwords, private keys, entire subscriber databases or unrestricted NAT archives. Ask for a private evidence-transfer method if a report requires sensitive material.
Account protection
Use distinct staff accounts and strong passwords. Keep recovery contact information current and restrict privileged actions to appropriate administrators.
If a device or account may be compromised, notify the organization administrator promptly and identify the affected sessions or integrations.
Network management
Remote router access requires verified ownership and an authenticated management route. Review the impact of reboot, disconnect and policy changes before execution.
Keep management destinations, credentials and tenant context consistent across background jobs and external systems. Treat unknown external results as unresolved until their outcome is checked.
Incident handling
Initial handling should verify the report, contain the affected access, preserve relevant evidence and assess which organizations or records may be affected.
Notification requirements and recovery actions depend on the incident, applicable law and contractual obligations. Acknowledgement time, incident response targets and security certifications require explicit confirmation before being advertised.
Research coordination
Use an agreed scope for testing and minimize access to personal information. Stop a test if it begins affecting another tenant or service availability, and report what happened.
This page provides a reporting channel. It does not create a bug-bounty promise or authorize testing outside an agreed scope.