bastion

Cybersecurity Ethics and Professional Responsibility

Build this skill

Decide the ethical response to a discovered vulnerability or monitoring request, and report a weakness through responsible disclosure.

One digit in a web address

Riya Menon is checking her semester results on her college portal, the website her college runs for students, when she notices that the web address ends in her roll number, roll=21CS047. Out of curiosity she changes the 7 to an 8, and the page now shows a classmate's name, marks and phone number. She has found a vulnerability, a weakness that lets someone do what they should not be able to do. Finding it took two seconds. What she does next is a question of cybersecurity ethics: the principles that guide what you should and should not do with the access and knowledge you have, even when nothing technical stops you.

Riya 2nd-year CS student …/marks?roll=21CS04 8 Semester results Name: S. Kale CGPA: 7.9 Phone: 98xxxxxx12 Not her record ✕ College portal: one digit changed What now? ✓ Report it privately to the college IT team, then stop Bug fixed. Riya is thanked. ! Post it on the class group "see how bad our portal is" Classmates' data exposed. ✕ Use it copy records or change marks An offence. Expulsion, police.

The discovery is the same on all three roads. Only the choice afterwards decides whether Riya helped, hurt her classmates, or committed an offence.

Three roads from the same discovery

On the first road, Riya stops, writes a short private note to the college IT team explaining what she saw, and does not look at any more records. The college fixes the page and nobody's data goes further. On the second road, she posts a screenshot to her class WhatsApp group to show how careless the portal is. Her intention may be good, but the screenshot exposes a classmate's phone number, and now two hundred people know a trick that works on every student's record before the college has had a chance to fix it.

On the third road, she uses the weakness: she pulls up every record in her batch, or tries to see whether she can change a mark. That is no longer curiosity. Looking at data you are not allowed to see, copying it or changing it is unauthorised access, which is an offence under Indian law, and it is also the kind of act a college disciplinary committee takes very seriously. The skill used on all three roads is exactly the same. What separates them is permission, intent and the harm done to other people.

Responsible disclosure, step by step

The first road has a name. Responsible disclosure, also called coordinated disclosure, means telling the owner of a system about a weakness privately, giving them reasonable time to fix it, and only talking about it publicly, if at all, once people are safe. It is like noticing that the lock on your neighbour's gate is broken. You tell the neighbour quietly; you do not put up a notice in the society lift saying which gate is open.

Noticesomething iswrongStoplook no furtherReportprivately, tothe ownerWaittime to fix itShareonly once safe

Each step protects someone: stopping protects other people's data, reporting privately keeps the weakness away from attackers, and waiting gives the owner time to fix it.

Many organisations publish a vulnerability disclosure policy, a page that says how to report a weakness, what kind of testing is allowed and that honest reporters will not be punished. Some go further and run a bug bounty, paying a reward for well-written reports. Neither gives anyone permission to go beyond what the policy allows. A good report is short and factual: which page, what you did, what you saw, and the fact that you stopped. It never includes copies of other people's data. Put the steps of Riya's report in the order she should follow, and notice what each one protects.

Permission is the line

Security work often means doing things that look exactly like attacks: guessing passwords, probing websites, reading logs full of private details. An ethical hacker, someone paid to find weaknesses before criminals do, uses the same skills as a criminal. The difference is written permission that says what may be tested, when, and by whom. Without it, the same action is an intrusion.

Think of an electrician you give your house keys to so he can fix the wiring. He may enter every room he needs, but he does not open the steel almirah, read your letters or come back next week without asking. Ethical security practice works the same way, and five habits capture most of it.

Get permissionIn writing, before testingStay inside what was agreedTouch the minimumSee only what the job needsNever keep copies of dataKeep secretsWhat you see at workstays at workDo no harmNo crashing live systemsNo changing real recordsBe honestReport what you found,including your mistakes

Each habit limits what a trusted person does with the access they have been given.

Watching to protect, or watching too much

Neha Kulkarni, Tulsi Health's IT and security lead, can see logs of every staff login and, as an administrator, could open any staff mailbox. Some monitoring is part of protecting the company: an alert when an account logs in from another state, or a check that customer files are not being emailed outside. Surveillance is when watching goes beyond what security needs, such as reading a pharmacist's personal messages to see whether she is job hunting. Privacy is a person's right to control information about themselves, and staff do not lose it when they walk into work.

The difference is like a housing society's gate register. Writing down who enters and when keeps everyone safe; searching residents' shopping bags does not. Fair monitoring is proportionate to a real risk, open (staff are told what is watched and why), limited to the people who need to see it, and kept only as long as needed.

Security monitoringTied to a real riskStaff told what is watchedFew people see resultsDeleted after a set timeSurveillanceCuriosity or controlDone in secretShared with anyoneKept forever

The same tool, such as reading mail logs, can fall on either side. The purpose, openness and limits decide which.

Locks that protect everyone, including the wrong people

Encryption scrambles data so that only someone with the right key can read it. It keeps Mrs. Lata Gokhale's prescriptions safe on Tulsi Health's servers and Riya's chats private on her phone. The same lock also hides the messages of criminals, which is why governments sometimes ask for a backdoor, a hidden way for authorities to unlock encrypted data. This is a genuine ethical debate. The difficulty is that a backdoor is like a master key to every flat in the city kept in one office: if it is stolen or misused, everyone is exposed at once, not only the criminals.

For a security professional the practical ethics are clearer. Use strong encryption for the people whose data you hold, never weaken it quietly for convenience, and follow lawful requests through proper legal channels rather than informal favours.

A responsibility to people you never meet

Security work protects people who never see it: a grandmother ordering medicines, a patient whose hospital records must be available at night, a family whose savings move through UPI. That is the societal responsibility of the field. It means warning people clearly without frightening them, designing safety for those least able to protect themselves, and refusing work that harms the public even when it pays. The choices below come from one month of Riya's internship at Tulsi Health. Each wrong first choice becomes an incident, so think about who could be harmed before you pick.

Follow your curiosity.

↑ ↓ to explore · Enter to open · Escape to close