NepalInformation Technology Guidelines for Commercial Banks, Monthly Report of Electronic Attacks
Nepal Rastra Bank Information Technology Guidelines, August 2012, Fraud Management
archived copy
Read from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived 2026. Publisher's page: https://www.nrb.org.np/bfr/it-guidelines-2012/In force.
A vulnerability and incident reporting rule binding private bodies.
- Instrument type
- a regulation made under an act
- Obligation class
- Reporting
As of .
What it requires
- This binds commercial banks licensed by Nepal Rastra Bank (reached by declaring that you are a bank). The Guidelines state that banks should compulsorily comply with them.
- Identify and document all electronic attacks and suspected electronic attacks in your system, and report them to Nepal Rastra Bank monthly (Fraud Management, item 1).
These lines are LexLint's reading of the law's text, as of .
Who enforces it
Enforcement body
Nepal Rastra Bank, which examines compliance with the Guidelines during periodic onsite and offsite supervision.
Settledness
- As of
- Open questions
- Is a guideline issued by the Bank Supervision Department an order, directive or circular of Nepal Rastra Bank under section 79(2) of the Nepal Rastra Bank Act, 2058, so that section 99(1) of that Act reaches a breach of it?
What this law does
The Guidelines say that banks should compulsorily comply with them. The Fraud Management part of the Guidelines calls for banks to identify and document all electronic attacks and suspected electronic attacks in their system and to report them to Nepal Rastra Bank monthly. Section 99(1) of the Nepal Rastra Bank Act, 2058 lets the Bank fine a commercial bank that violates an order or directive issued by the Bank, up to the amount related to the violation.
When LexLint raises it
When your app profile says your app is a bank.