Best Practice Checklists

An exclusive publication of

Essentials every leader should understand about IT


Issue 12 – IT Policies and Management Practices

IT Policies and Management Practices — download the printable PDF

Download this article as a PDF

Click Here to Download
Contact Us

IT Policies & Management Practices

The quiet paperwork that decides how a bad day ends

Policies and management practices rarely feel urgent. They are easy to defer, because on an ordinary day nothing seems to depend on them. Yet when an employee leaves, a vendor is compromised, or an attacker gets in, the documents you wrote, or never wrote, largely decide how quickly and cleanly the organization recovers. They also shape the exposure to liability that can follow a data breach.

When it goes wrong

The scenarios below are not exotic. Each is an ordinary gap in process or documentation, the kind that stays invisible until the day it matters. The goal here is not to alarm, but to show what these quiet practices are actually protecting against.

The Account That Outlived the Employee

A staff member is let go on a Friday. HR completes the exit paperwork, but no formal handoff reaches IT, so the person’s VPN credentials and cloud mailbox stay active. Weeks later, files are accessed from outside the office.

Access no one remembered to revoke becomes the way back in.

A Breach With No Plan

A finance staffer opens a convincing invoice. By the time the intrusion is noticed, who to call, what to disconnect, and who must be notified are all being decided in the moment, under pressure. Hours are lost deciding rather than acting.

The costliest part of many breaches is the scramble, not the intrusion.

The Service Account Nobody Owns

A third-party application was set up years ago with a standing administrative account and broad permissions. The consultant who configured it is long gone, no one documented what it can reach, and it has never been reviewed.

An account no one owns is an opening no one is watching.

The common thread

None of these is a failure of firewalls or antivirus. Each traces back to something that was never written down: a procedure, an owner, or a plan. Policy is what turns knowledge held by one person into something the organization can still rely on when that person is out, or gone.

Every one of these outcomes turned on a document that did not exist, or a responsibility no one had been assigned. Policies and management practices are not paperwork for its own sake. They decide, in advance, how an ordinary bad day ends.

What to Ask Your IT Manager or Provider

and how to know if the answers are good ones

You do not need to write these policies yourself to make sure they exist. You need to know what to ask. Run the checklist below with your IT professional. Where an item touches legal obligations or employment matters, it is prudent to involve qualified legal counsel as well. If any item is not marked green, it may warrant a closer look.

Know what you have

Network Documentation

✓
–
?
Does the organization maintain current documentation of its network, including diagrams, rack elevations, and detailed hardware and software asset inventories? Documentation is the reference nearly every other practice depends on. When it is missing or out of date, troubleshooting, planning, and secure staff transitions all take longer and carry more risk. Network documentation is covered in depth in Issue 11 of this series.

Asset Tagging & Tracking

✓
–
?
Are company IT assets tagged and tracked in an asset management system? Formal tracking helps reduce loss and supports a planned replacement cycle, so equipment is refreshed near the end of its useful life, commonly around three to four years, before age and hardware degradation drive up maintenance overhead and downtime.

IT Budget & Forecasts

✓
–
?
Does the organization prepare and maintain annual IT budget forecasts? Budgeting helps ensure that systems continue to meet the organization’s needs, that hardware and software upgrades happen on time, and that contingency funds are set aside for incident response when they are needed.

People & access

Onboarding & Termination Procedures

✓
–
?
Are formal procedures in place for communicating onboarding and termination requirements between HR and IT? Clear procedures tell IT what to create, what to assign, and, just as important, what to remove and when. Without them, time is lost clarifying instructions or correcting mistakes, and accounts or permissions that are not promptly removed can become a serious point of exposure.

Documenting Non-Standard Configurations

✓
–
?
Does the organization document all non-standard configurations, such as power users, administrators of third-party solutions, and social media accounts? Without a complete picture of each user’s rights, it is easy to inadvertently grant access that should be restricted, or restrict access that is authorized, when people change roles or leave. Documentation should cover internal rights, including Active Directory rights and group inheritance, VPN access, and non-standard access to systems such as ERP, accounting, and payroll, as well as access to external systems, from third-party mail hosts to social media accounts.

Acceptable-Use & IT Policies

✓
–
?
Does the organization maintain, and update as needed, formal policies governing the use of its IT systems? These policies vary by organization and tend to change as new technologies and legislation emerge. The topics below are commonly recommended for inclusion, subject to prior review and approval by qualified legal counsel:
  • Employee responsibilities for safeguarding passwords.
  • Practices for protecting confidential information.
  • Physical security of equipment (laptops, smartphones, and similar devices).
  • Proper use of and access to systems, with responsibilities and limitations.
  • Prohibitions against unauthorized technical changes and modifications.
  • Restrictions on the unauthorized use of software, web services, and equipment not provided by the company.
  • Virus awareness and avoidance.
  • Responsibility to attend company-sponsored employee and contractor security training and awareness.
  • External media handling and disposal.
  • International travel security.
  • VPN and mobile device use.
  • Unlawful or unauthorized use of systems.
  • Unauthorized removal, copying, deletion, or dissemination of information.
  • Electronic use of the company logo and branding imagery.
  • Blogging and social media use.
  • Compliance with copyright law.
  • Confidentiality policies and guidelines.
  • Restrictions governing torrents and questionable websites.
  • Inappropriate communications, harassment, and discrimination.
  • Company ownership of, and the right to monitor, view, and record, all information transiting company systems (including third-party hosting facilities, Cloud solutions, smartphones, and other connected devices, as applicable).
  • Employee and contractor privacy expectations when using company systems.
  • Post-termination employee and contractor conduct.
  • Return or destruction of company electronic information.
  • Duty to assist and to provide passwords as needed.

IT Department Security

✓
–
?
Does the organization have policies governing how its own IT function is administered? IT staff typically hold broad, sometimes unrestricted, access, which is a natural point of concentration and a common exposure in smaller organizations. Qualified hiring, background checks, and periodic audits all help reduce that exposure. Among the most effective controls are documented internal standards and tools that produce audit trails. Standards vary by organization and may address data sanitization, software approval, discrete assignment of administrative rights, Active Directory controls, and equipment and media disposal.

Vendors & data

Outside Vendor Security

✓
–
?
Is there a formal process for evaluating the security of third-party vendors before engaging them? A vendor security questionnaire gathers the information needed to judge whether a vendor’s security meets the organization’s standards. Useful data points include security audit results, development practices, system redundancy, support options and response times, upgrade schedules and maintenance windows, backup and retention policies, change management processes, and access requirements.

Vendor Audit Results

✓
–
?
Where available, are third-party vendor audit results reviewed? Many vendors fall under compliance regimes such as PCI DSS or FINRA and undergo periodic audits of both security and compliance. Vendors entrusted with sensitive information, or permitted to connect to your systems, should be able to speak to their compliance measures. Some publish this information; others will generally provide it on request.

Data Classification

✓
–
?
Does the organization have a system for classifying data by sensitivity? Data is difficult to protect consistently until it has been identified. Sensitive data commonly includes access credentials, HR and payroll information (such as Social Security numbers and direct-deposit bank details), sensitive client data, trade secrets, financial data, creative work, and internal forecasts.

Change Management

✓
–
?
Are formal change management procedures in place? Change management helps ensure that proposed changes to systems or workflows do not introduce new vulnerabilities, conflict with existing configurations, or cause unintended disruption to business operations.

Plans for when something goes wrong

Information Security Plan

✓
–
?
Does the organization have a formal information security plan? An Information Security Plan or Program (ISP) identifies risks, documents the safeguards in place, and defines the measures that make up a formal security program. It names who is responsible for overseeing data security and addresses staff management and training, how areas holding sensitive data are documented and secured, secure data destruction, detecting and managing system failures, and periodically reviewing and adjusting the plan. Some organizations are legally required to maintain one and may not realize it. The GLBA Safeguards Rule, for example, applies to organizations that prepare tax returns, and the FTC strengthened the rule in 2021, with certain requirements taking effect in June 2023. A separate 2023 breach-notification amendment took effect in May 2024. Because obligations of this kind vary and change over time, the specifics are best confirmed with qualified legal counsel.

Backup & Disaster Recovery Plan

✓
–
?
Does the organization have a written backup and disaster recovery plan? A BDR plan sets out the steps, the order of action, and each team member’s responsibilities in the event of a disaster. A well-prepared plan supports a faster, smoother response to a loss or failure, with the goal of minimizing both data loss and downtime.

Incident Response Plan

✓
–
?
Does the organization have a formal incident response plan for cybersecurity incidents? No environment is completely secure, and the sharp rise in social engineering attacks has led many experts to treat a serious breach as more a question of when than if. A written incident response plan sets out the steps, the sequence, and the responsibilities assigned to specific individuals, so the response is quicker and better coordinated. Acting from a plan rather than improvising can help reduce downtime, data reconstruction, forensic costs, mandatory notification expenses, legal fees, public-relations costs, reputational harm, and lost revenue, by containing exposure sooner.

Download the printable PDFReturn to checklists

To review how your organization measures up against these practices, it is recommended that you consult your Sandbox Technologies Engineer, Consulting CIO, or Account Manager. Not a client yet? Contact us here to get started.

Contact Sandbox Technologies for a free, no-obligation consultation.

Headquartered in Los Angeles. Serving clients nationwide and internationally since 1997.

Nationwide (Toll-Free)

877-930-8324

Los Angeles

424-207-5130

Support Helpdesk

424-207-5140

    By submitting this form you are confirming that you have read and agree to our Privacy Policy

    * NOTE: Hardware purchase requests submitted via this form will not be honored. Hardware sales are facilitated in support of established customer accounts only.