Skip to content

Beginner · Security basics · topic 5 of 43 · 25 min

Ethics and the law: permission first

Explanation

In security, the same action can be a job or a crime. The difference is permission. In India the IT Act 2000 makes unauthorised access to a computer a civil wrong (Section 43) and, when done dishonestly or fraudulently, a crime (Section 66). Practise only on your own lab machines, legal training platforms, or with written permission.

Why ethics comes first

Security people learn how attacks work so they can stop them. That knowledge is powerful. Scanning a server, guessing a password or reading someone's traffic is normal work in a lab or a paid test with permission, and a crime on someone else's system without it. A career in security is built on trust: one illegal "test" can end it before it starts.

The law in India: the IT Act, 2000

The Information Technology Act, 2000 (amended in 2008) is India's main cyber law. A few sections every security learner must know:

SectionWhat it covers (simplified)Consequence
43Without the owner's permission: accessing a computer or network, copying data, introducing a virus, damaging or disrupting a system, denying access to authorised users, and similar actsYou must pay compensation for the damage (civil liability)
66Doing any act in Section 43 dishonestly or fraudulentlyCrime: up to 3 years in prison, or a fine up to ₹5 lakh, or both
66CIdentity theft: fraudulently using someone's password, electronic signature or other unique identity featureCrime: prison and fine
66DCheating by pretending to be someone else using a computer or phone (impersonation)Crime: prison and fine

Fraud cases can also be charged under the Bharatiya Nyaya Sanhita (BNS), which replaced the Indian Penal Code from 1 July 2024. Other countries have similar laws, such as the Computer Fraud and Abuse Act in the USA and the Computer Misuse Act 1990 in the UK. "I was only testing" is not a defence anywhere.

Permission done properly

Professional testers work only with written authorisation from someone who actually owns the system and can give permission. The document sets out:

  • Scope: exactly which systems, IP addresses, domains or apps may be tested, and which may not.
  • Rules of engagement: what kinds of tests are allowed, at what times, and what is off-limits (for example no denial-of-service, no real customer data).
  • Contacts: who to call if something breaks or a real attacker is found.
  • Dates: when testing starts and ends.
Careful: Your company's IT manager cannot give you permission to test a cloud provider, a bank's payment page or a vendor's website, because the company does not own them. Permission must come from the real owner.

Where you can practise legally

  • Your own lab: virtual machines on your own computer, such as an Ubuntu VM, a Windows evaluation VM, or deliberately vulnerable apps like OWASP Juice Shop or DVWA.
  • Legal training platforms: TryHackMe, Hack The Box, PortSwigger Web Security Academy, OverTheWire, LetsDefend and CyberDefenders (blue-team practice).
  • Bug bounty programmes: companies publish a scope and rules and pay for reports. Read and follow every rule.
  • Capture the flag (CTF) events run by colleges and communities.

Ethics beyond the law

  • Confidentiality: what you see in logs and investigations stays private.
  • Do no harm: stop and report if a test starts to break something.
  • Responsible disclosure: if you find a bug by accident, report it privately to the owner (or to CERT-In) and do not exploit or publish it first.
  • Honesty: report what you actually found, not what sounds impressive.

Common mistakes

  • Scanning your college or office network "to learn" without asking. Even a scan can break old devices and break the rules.
  • Trying a "trick" you saw in a video on a real website.
  • Keeping copies of data you found during a test.
Tip: Defenders also need written approval for some work, such as capturing network traffic or reading staff mailboxes in an investigation. Get it in writing every time.

Need help?

Stuck on a word or an idea? Search this course, or every course, and jump straight to the explanation or a worked question.

Try:

Watch the lesson

Ethics and the law: permission first · 1/6

Permission makes it legal

In security, the same action can be a job or a crime. The difference is permission.

Prefer a video by a teacher? Find free videos on “IT Act 2000 section 43 66 explained cyber law India” on YouTube ↗

In real life: A student, a college portal and a lesson

A student notices that changing a number in the URL of the college results portal shows other students' marks. Testing further, downloading records or posting about it could fall under Sections 43 and 66. The right action is to stop, write down only what was seen by accident, and report it privately to the college IT team. Many organisations now publish a security contact or a responsible disclosure page for exactly this.

Practice (0/2 done)

Task 1 · Question

Which of these is legal practice?

Task 2 · Practice

Write a one-page "rules of engagement" for a pretend test of your own home lab. Include the owner, the scope, what is not allowed, dates, and an emergency contact.

Quick quiz

Question 1

1.Under the IT Act 2000, which section covers unauthorised access and damage with compensation?

Question 2

2.What turns a Section 43 act into a Section 66 offence?

Question 3

3.Who can authorise a security test of a website?

Question 4

4.You find a bug by accident on a company website. What should you do?

Read more (free)

Before this, learn

This topic builds on these. If something here feels new, open them first.

Open a question to see the answer and why. The first ones are this topic's own quiz, so try the quiz above before you peek.

Under the IT Act 2000, which section covers unauthorised access and damage with compensation?

Answer: Section 43

Section 43 sets civil liability (compensation) for unauthorised access, copying, damage and similar acts.

What turns a Section 43 act into a Section 66 offence?

Answer: Doing it dishonestly or fraudulently

Section 66 applies when the Section 43 act is done dishonestly or fraudulently.

Who can authorise a security test of a website?

Answer: The owner of the system, in writing

Only the true owner (or someone they formally authorise) can give permission, and it should be written.

You find a bug by accident on a company website. What should you do?

Answer: Stop, and report it privately to the owner or CERT-In

Responsible disclosure: stop, keep only what you saw, and report privately.

Section 43 of the IT Act is best described as…Related

Answer: A civil liability to pay compensation for unauthorised access/damage

Section 43 is civil: compensation for access or damage done without permission.

From The law in India: IT Act 2000, sections 43 and 66

A "grey hat" who finds a bug on a stranger's site without permission is…Related

Answer: Still acting illegally

No permission means it is illegal, whatever the intention.

From What ethical hacking is (and is not)

A switch still runs old software with a known bug. What is the bug called?Related

Answer: A vulnerability

A vulnerability is a weakness. A threat is something that could use it.

From Security basics: threats, CIA and AAA

If a service becomes unstable during a test, you should…Related

Answer: Stop and contact the client immediately

Stop and use the emergency contact in the RoE.

From Post-exploitation ethics: what to do once you are in

Pass the quiz (60% or more) or mark this topic as done when you are ready.

Your progress is saved on this device only.

Next steps

  1. This is the last topic of “Security basics”. The module exam comes next.
  2. Module 1 exam: Security basics · 13 questions · 20 min, without help. 5 topics of this module still to finish first.
  3. Then the next module, Networking for security. 43 topics left in the course before the final exam.

← Previous: Phishing and social engineering