bastion

Organizational Security Policies and Practices

Build this skill

Decide whether everyday workplace actions comply with acceptable use, BYOD and approved-software policies, and explain why shadow IT appears and how to remove its cause.

The rulebook that keeps fourteen stores on the same page

On a busy afternoon at the Nashik Road store, Arjun Pawar needs to send forty supplier invoices to Sameer Joshi in accounts. The shared drive is slow on the store Wi-Fi, so a colleague suggests a free file-sharing app he used in college: drop the files in, copy a link, done in a minute. Arjun has just made a security decision without noticing it. Whether that decision was allowed, and who should have made it, is settled by a security policy: a written set of rules, approved by the organisation's leaders, that says how people must use its computers, systems and data. Policies turn a vague "be careful" into specific expectations that every employee in every store can follow the same way.

What a policy is, and what makes one work

A policy states what must happen and why, in words everyone can understand. It is usually backed by two more detailed kinds of document. A standard sets a specific, measurable requirement, such as "passwords are at least 12 characters". A procedure gives the exact steps, such as how a new pharmacist asks for access to the shared drive. Think of a housing society in Pune. The society's rules say every visitor must be recorded, the gate register is the standard way of recording them, and the watchman's routine of asking for name, flat number and phone number is the procedure. Without the rule, the watchman has no authority to stop anyone at the gate.

Good policies are short, specific and owned. Short, because nobody follows forty pages they have never read. Specific, because "use systems responsibly" tells nobody what to do, while "do not install software on billing laptops; ask IT" does. Owned, because someone, at Tulsi Health Neha Kulkarni as IT and security lead with Vikram Deshmukh's approval, must keep each policy up to date and answer questions about it. A policy that is never explained, checked or updated is just another file on the shared drive.

Acceptable useWhat company laptops, email andWi-Fi may be used forSigned by every new joinerBring your own deviceRules for personal phonesthat carry work emailLock, update, report lossApproved softwareOnly tools IT has checkedmay hold Tulsi dataAsk before you install

Each policy answers one everyday question: what may I do with company systems, what about my own phone, and which apps may I use for work.

Acceptable use: what company systems are for

An acceptable use policy, or AUP, says what employees may and may not do with the organisation's computers, network, email and data. The network here simply means the connections that link the store's laptops, router and internet together. For Tulsi Health the AUP says that billing laptops are for billing and stock, not personal browsing or games. Staff never share their logins. Customer records are opened only to serve that customer, and the staff Wi-Fi password is never given to customers, who use the separate guest network. Most organisations ask new staff to read and sign the AUP when they join, and to confirm it again each year.

The AUP matters because many incidents begin with an ordinary action that seemed harmless. A pirated film downloaded on a counter laptop can carry malware, software written to cause harm. A pharmacist curious about a neighbour's prescriptions is misusing customer data even if nothing leaves the building. Without a written rule, the company has no clear way to say either was wrong, and the employee had no clear way to know. The AUP also protects staff: someone who followed it and was still fooled by a clever attack has done what was asked of them.

BYOD: staff phones that carry work email

Several Tulsi Health staff read work email on their own phones. This is BYOD, short for bring your own device: employees using personal phones or laptops for work. It is convenient and saves the company money, but the company's data now sits on a device it does not own. That phone may have no screen lock, may be handed to a younger cousin for games, and may be left behind in an auto-rickshaw. A BYOD policy sets the conditions a personal device must meet before it can touch work data.

What Tulsi asks of your phoneScreen lock with a PIN or fingerprintPhone software kept up to dateTwo-step login on work emailReport a lost phone within hoursWhat Tulsi can and cannot doCan erase the work profile onlyCan see if the phone is up to dateCannot see your photos or chatsCannot read your personal apps

Staff accept rules on their own phones far more readily when the policy says just as clearly what the company will never touch.

A typical BYOD policy for work email asks for a screen lock, an up-to-date operating system (the phone's main software, such as Android or iOS) and two-step login on the mail account. In return the company limits itself. On most modern phones work apps can live in a separate work profile, a walled-off area of the phone, so IT can erase work email from a lost phone without touching family photos. The policy should state plainly what the company can see and what it cannot, because staff will quietly ignore rules they suspect are a way of spying on them.

Shadow IT: the app nobody approved

Back at Nashik Road, the free file-sharing app is an example of shadow IT: software, apps or online services used for work without the IT team's knowledge or approval. It nearly always starts with good intentions. Someone has a job to do, the approved tool is slow or awkward, and a free alternative is one download away.

Nashik Road store · 3:10 PM Arjun, store manager Free file-share Invoice_Oct_01.pdf Invoice_Oct_02.pdf + 38 more invoices Copy share link what happened approved path Shadow IT: unapproved app ✕ Server run by an unknown company ✕ Anyone with the link can open ✕ Not in the nightly backup ✕ Neha's team cannot see it Approved: Tulsi shared drive ✓ Staff login with two-step ✓ Included in the nightly backup ✓ Access removed when staff leave ✓ Shows who opened each file

The free app saved Arjun a few minutes, and quietly removed every protection the approved shared drive gives Tulsi Health's invoices.

The trouble is everything the free app does not do. The invoices now sit on a server, a computer that stores files for many users, run by a company Tulsi Health has no agreement with. Anyone who gets the share link can open them, and links get forwarded. The files are outside the nightly backup, and when an employee leaves, nobody removes their access because nobody knew the account existed. If that app is ever breached, Neha will not even know Tulsi's data was involved. The fix has two sides: the policy forbids unapproved tools, and IT fixes the reason people reached for them, here by making the shared drive usable on store Wi-Fi. When many people keep breaking the same rule, it is often a sign that the approved path is too hard.

Everyone's part, and how compliance is checked

Policies spell out employee security responsibilities, the things every person must do whatever their job. Lock the screen when leaving the counter. Use only your own login. Report suspicious emails and lost devices quickly. Keep customer data inside approved systems, and finish the yearly security awareness training. None of these needs technical skill, a bit like keeping your own luggage in sight on an overnight train: simple, personal, and effective only when everyone does it.

Policy compliance means that people and systems actually follow the policy, and that the organisation checks that they do. Checking can be gentle and regular: each quarter Neha's team reviews which apps are installed on billing laptops, sees which staff have finished training, and spot-checks whether counter screens lock on their own. When someone breaks a policy, the response should match the cause. A mistake made in a rush calls for coaching and perhaps a better tool, while repeated or deliberate misuse, such as snooping in customer records, calls for the formal action the policy describes in advance.

Writeshort, specificrulesExplaintraining,sign-offFollowdaily workCheckreviews, spotchecksImprovefix rules andtoolsevery year, or after an incident

A policy keeps working only while it goes round this loop. Checking finds where people struggle, and improving fixes the rule or the tool, not just the person.

Now take the seat of the person checking compliance. Each card below is something a Tulsi Health employee did last month. Decide whether it follows the policies described above or breaks them, then check your sorting and read why.

Follow your curiosity.

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