Partners can show that daily security controls match a Written Information Security Plan by connecting each plan requirement to an owner, a recurring task, and dated evidence. Review real account changes, vendor access, backups, staff reporting, and incident handling against the written procedure. Record exceptions and corrective actions so partners can see what happened and what changed.
In This Article
- Why can a written plan drift from the way the firm actually works?
- Which everyday records help partners verify that controls are operating?
- How should a firm handle access changes across legal and practice software?
- What should partners check about vendors, backups, and incidents?
- How can Carmel partners make the review useful without adding busywork?
- Frequently Asked Questions
Why can a written plan drift from the way the firm actually works?
A WISP can describe a sound process while daily work follows a different path. A new employee may receive access before the approval record is complete. A departing employee's account may remain active because several applications have separate sign-in processes.
These gaps often appear at handoffs. A partner approves a change, an office manager handles onboarding, and an outside IT provider changes system access. If the plan does not say who owns each step, the firm may have no reliable way to show that the control occurred.
Start with the work that moves sensitive information. For a law firm, that may include matter-management software, document storage, email, remote access, and client portals. For a medical practice, it may include the systems used to handle patient information and the staff access needed for scheduling and care workflows.
The Indiana Consumer Data Protection Act may affect how a business evaluates privacy and security obligations. HIPAA, PCI, and CMMC requirements depend on the organization's industry and contracts. A WISP review should identify the rules that actually apply to the firm rather than assume one checklist covers every business.
One practical test: every recurring control should have a named owner, a defined trigger or schedule, and evidence that can be retrieved.
The gap is usually in ownership and follow-through, not in the wording of the plan.
Which everyday records help partners verify that controls are operating?
Evidence should come from work the firm already performs. A polished policy document cannot establish that an access review occurred or that a backup was checked. Look for ordinary records that show the control's date, scope, outcome, and follow-up when something did not go as expected.
Useful evidence may include approved access requests, account changes, documented exceptions, backup status records, staff training attendance where recorded, vendor access approvals, and incident or service records. Keep the evidence proportionate to the control. A short, dated review record may be more useful than a large folder of screenshots with no explanation.
For each control, ask whether a reviewer can answer four questions: what was checked, who performed or approved it, when it happened, and what occurred if it failed. If the record answers only "we normally do this," it does not establish that the control operated on a particular occasion.
Protect the evidence itself. Limit access to people who need it, avoid collecting unnecessary personal or client information, and use a consistent location the firm can retrieve during a partner review. The objective is a traceable record, not an expanding archive of sensitive material.
A compact evidence register can keep the review manageable:
- Write the control in plain language and point to the WISP section that describes it.
- Name the operational owner and any approver.
- Identify the record that demonstrates completion, including where it is kept.
- Note the review date and any exception, assigned corrective action, or completion date.
Consistent, minimal records are easier to maintain and easier to explain.
How should a firm handle access changes across legal and practice software?
Access control is not one setting in one system. A person may have separate permissions in email, document management, a case or practice platform, remote access, and a client-facing portal. The WISP should describe how the firm approves, changes, and removes access across the systems that matter to its work.
For onboarding, retain the request, the approval, and a record of the access assigned. For role changes, document what changed and why. For departures, keep evidence that the firm initiated access removal and checked the relevant systems. If an application has its own administrator, identify who confirms that its account was addressed.
Partners should also review exceptions. A temporary account, shared workflow, or elevated permission may be operationally necessary, but it should have an owner and a reason. Set a review or removal point when appropriate. An undocumented exception can become permanent simply because no one knows who is responsible for it.
GDS Technology describes its Identity and Access Security work as helping customers review and improve agreed identity and access controls around business systems. The stated scope includes account inventory, access review, authentication configuration, role and permission review, lifecycle procedures, and change documentation. That work does not replace the firm's responsibility for legal compliance decisions.
Good access records connect a person's work responsibilities to the permissions they actually have.
What should partners check about vendors, backups, and incidents?
Third parties can handle information or provide access to systems the firm depends on. Keep a current record of relevant providers, the services they support, the information or access involved, and the firm contact responsible for the relationship. When a provider's role changes, review whether the WISP's safeguards and contact details still reflect the arrangement.
Backup evidence should show more than that a backup job was configured. Record whether the expected jobs completed, who reviews failures, and what happens when a recovery test or restoration is needed. The firm should know which systems and information are covered and who coordinates recovery decisions. Do not treat a green status indicator as proof that every business process can be restored.
Incident procedures need a usable route from the first report to the people who make decisions. Staff should know how to report a suspicious message, unexpected account activity, lost device, or possible disclosure. The plan should identify who receives the report, who preserves relevant records, and who decides whether outside counsel, insurers, regulators, or affected parties need to be involved.
GDS Technology offers disaster recovery planning and data backup and recovery services. The appropriate scope depends on the firm's systems, responsibilities, and recovery priorities. Partners should confirm that any provider's written scope matches the controls and records the firm expects to maintain.
Test the handoffs that matter before an incident forces the question.
How can Carmel partners make the review useful without adding busywork?
Use a short, repeatable review tied to the firm's actual operating calendar. A review can be triggered by a major system change, new vendor access, a role change, a reported incident, or a planned partner review. The right cadence depends on the firm's WISP and obligations; do not claim a universal frequency where the plan or applicable requirement does not specify one.
Choose a sample of recent work rather than asking staff to recreate months of activity. Check whether the record exists, whether it matches the written procedure, and whether an exception was resolved or assigned. If the plan calls for an approval, a completed technical change without that approval is a mismatch to investigate, not a reason to quietly rewrite the evidence.
A real service example illustrates why follow-through matters. Therese, a commercial real estate client, said, "Brian clearly explains what is happening and shows you ways to help prevent the issue from happening again. He is great to work with." The same practical habit applies to control reviews: explain the issue, identify the cause, and document the prevention step rather than closing the item without learning from it.
When a control does not match the plan, decide whether the process failed, the plan is outdated, or the evidence is incomplete. Assign an owner and due date for the correction. If the intended process has changed, update the WISP through the firm's approval process and retain the prior version according to its document practices.
For local firms, the building and work pattern can shape the review. A practice with staff moving between offices, remote work, or shared premises should account for the systems and physical access involved in its own operations. Carmel City Center or Midtown Carmel is context, not a control: the relevant question is which people, spaces, devices, and services the firm actually relies on.
Keep the review focused on decisions that protect client service and keep work moving. A useful starting point is the firm's existing WISP, followed by its access procedures, backup records, incident contacts, and vendor list. GDS Technology's FTC compliance services and IT compliance services pages describe related service areas. Carmel firms can also review the Carmel, Indiana location page.
Ask whether the evidence would let another partner understand the control without relying on someone's memory.
More on this from Built Wired Secured - Blog: OT Security Assessment for Building Operations.
Frequently Asked Questions
What does a WISP control review need to prove?
It should connect a requirement in the written plan to the person responsible, the work performed, and a dated record showing the result. When a control fails or an exception occurs, the record should identify the follow-up and its owner. A review demonstrates how the firm operates; it does not by itself establish legal compliance.
How can a small firm document access changes without creating excess paperwork?
Use existing approval and service records where they capture the requester, approver, systems affected, change date, and completion. Keep a separate note only for information those records do not provide, such as an exception or follow-up. The goal is a retrievable trail that matches the WISP, not duplicate forms for every technical step.
Does an Indiana business need to follow the Indiana Consumer Data Protection Act?
Applicability depends on the organization and the law's requirements. A business should not assume that location alone determines its obligations. Partners can ask counsel or a qualified compliance adviser to assess applicability, then ensure the WISP and operating controls reflect the requirements that apply to their organization and contracts.
How often should partners compare daily controls with the WISP?
Use the review schedule stated in the firm's plan and any applicable obligations, and revisit controls when important business or technology changes occur. Examples include a new system, vendor, access model, or incident. If the plan does not specify ownership or timing, clarify those details through the firm's approval process rather than inventing a universal schedule.
What should a firm do when its evidence does not match its WISP?
First determine whether the control was missed, the evidence is incomplete, or the written procedure no longer reflects approved practice. Record the finding, assign a responsible owner, and track the corrective action to completion. If the process has changed, revise the WISP with appropriate approval and preserve a clear record of the change.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.