A Short, Plain IT Policy Your Staff Will Actually Read

IT policy for employees in seven steps

Many offices run without a written IT policy. Staff install whatever tools they like, send files to personal email, share passwords and are not sure what to do when something looks wrong. A recent Affix Center guide explains how to close this gap with a short document, not a long legal one.

What the policy should cover

  • Acceptable use of company laptops, email and internet
  • Individual logins, password standards and multi-factor authentication
  • Approved software and rules for personal devices
  • Where data may be stored and how it may be shared
  • Remote work, including VPN and screen locking
  • Which incidents to report, to whom and how fast
  • Giving and removing access when people join and leave

Seven steps to roll it out

Start by listing your devices, software, cloud services and who holds admin access. Next, spend about an hour each with HR, finance, sales and operations to learn how people really work. Write the rules in plain language using "you must" and "you must not", and aim for 6 to 10 pages that can be read in 20 minutes. Back every rule with a tool or process, because a rule nobody enforces becomes a suggestion. Get a director or the CEO to sign it, train staff and collect their acknowledgement, and review the policy every year.

The guide also notes why timing matters: CERT-In's 2022 directions require incident reporting within six hours, and the DPDP Act expects reasonable security safeguards.

Read the full seven-step guide here: No IT Policy for Employees? Fix It in 7 Steps

Published by Affix Center, a Mumbai-based IT services company that helps organisations with IT governance through its enterprise advisory practice.

Comments

Post a Comment

Popular posts from this blog

Self-Hosted GitLab? CVE-2026-97229 Is Being Exploited, Check Your Version

Image
If your team runs its own GitLab server, this one needs attention this week. CVE-2026-97229 is a CVSS 10.0 integer overflow in the regular expression compiler used by GitLab CI/CD. A crafted regex in a CI/CD configuration can let an attacker run code on the server. GitLab shipped fixes on 12 October 2026, and CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 29 October 2026. Which versions are affected 19.2 branch: fixed in 19.2.8 19.3 branch: fixed in 19.3.5 19.4 branch: fixed in 19.4.2 GitLab.com and GitLab Dedicated are already patched The root cause sits in Onigmo, the regex engine inside Ruby, so source or custom builds with their own Ruby may need a separate Ruby update. A short action list List every self-managed GitLab instance, including test and forgotten ones Upgrade each one to the fixed version for its branch Turn off open sign-up and limit who can push to public projects until patched Review recent .gitlab-ci.yml changes, unknown users and o...
Read more

Hiring a Website Developer? Six Warning Signs to Spot Before You Sign

Image
Many business websites get built twice. The first vendor wins on price, and a few months later the site is slow on mobile, the contact form stops working, and nobody can reach the developer. Most of this can be avoided with the right questions before signing. Warning signs in a website quote A fixed price given before anyone asks about content, integrations or users No live examples, or examples that no longer load Reluctance to register the domain and hosting in your company's name No mention of testing, backups or updates Pressure to sign fast with a "this month only" discount A launch plan with no redirects for old URLs, which can wipe out search traffic What to ask for instead An itemised proposal: pages, templates, features, integrations, revisions, testing, hosting and support A meeting with the project manager and lead developer, not only sales Written ownership of domain, hosting, source code, design files and content A short paid discovery phase that p...
Read more

Laravel Projects That Need a Rebuild After 18 Months: Five Causes and How to Avoid Them

Image
A common story: a business picks a Laravel vendor for a low quote, and about eighteen months later the app is slow, small changes break other features, and the next vendor says it must be rebuilt. Laravel is rarely the problem. The way the vendor was chosen usually is. Five causes behind costly rebuilds Business rules stuffed into controllers, so a new GST field touches many files No automated tests, even though Laravel supports PHPUnit and Pest The N+1 query problem: a list of 100 orders running 101 queries Security left to chance: debug mode on in production, or secrets stored in the code repository The vendor, not the client, holding the repository, servers and domain Version support matters too Per the official Laravel documentation, each major release gets bug fixes for 18 months and security fixes for 2 years. Laravel 13 came out in March 2026, and security support for Laravel 12 runs until February 2027. Plan upgrades in your maintenance contract. Before you sign Have an ...
Read more