How should I audit a neglected IT setup for ISO 27001 readiness?

November 19, 2026 5 answers
Asked by 7e+socketgauge_593

I'm reviewing our external IT setup, licensing and costs as we start preparing for ISO 27001. We have standalone Windows servers in a workgroup and a Remote Desktop server, but I can't see why we still need it.

Our provider says we have on-premises Active Directory without a domain controller, and the RDS licensing manager shows no issued user CALs. What should I check first, and how do I tell what's actually compliant?

Answers

r.813!cobaltwhisk

Ask the provider to show you the directory and explain exactly what they mean by Active Directory. On-premises Active Directory Domain Services needs at least one domain controller. A workgroup doesn't provide domain-based centralized account management, though a server can still run other services without joining a domain.

That doesn't prove the provider is deliberately misleading you. There could be a misunderstanding about a different directory service or a domain elsewhere. Get a diagram, server names, roles and an explanation you can verify rather than settling for a vague answer.

Reply to this answer
8k~copperfob_356

Start with an inventory and a safety check before changing anything. List the servers, services, accounts, software, support dates, licenses and who has access. Make sure the company has the administrative credentials it needs, stored securely.

Then check the backups. Find out what's covered, where copies are kept and whether a restore can be demonstrated. Also look at patch status, endpoint protection and how accounts are created and removed. A configuration that works today isn't much comfort if nobody can recover it or show that updates are actually succeeding.

If the current provider can't document and demonstrate the setup, bring in an independent, experienced administrator to assess it. That doesn't mean you have to rebuild everything immediately.

Reply to this answer
m.483+vexdali

Zero issued user CALs is not proof that no licenses are required or that the setup is compliant. Gather purchase records, Windows Server and RDS versions, licensing mode, and the number of users or devices accessing the services. Have a qualified licensing specialist or reseller review the details against the applicable Microsoft terms.

Being fully on-premises doesn't remove licensing obligations. Also check the older products' support status separately from whether you own valid licenses.

Reply to this answer
_h83~draxelo.5

Don't switch off Remote Desktop just because the apps are web-based. Check who's connecting, what they run, which files or printers they use and whether it serves a remote access or support purpose. Ask users too, since an occasional workflow may not be obvious from a quick look.

If it has no real job, plan a retirement and test the replacement first. If it stays, review access, account management and licensing. Cloud-managed devices might fit, but an on-premises domain could also be reasonable. The right choice depends on the actual workload and requirements.

2u~gobletcompass_714:

Check dependencies before removing the server too. A file share or scheduled task might be relying on it even if nobody uses a desktop application there.

Reply to this answer
q.368!ferrulepouch

ISO 27001 is broader than whether Windows machines are domain-joined. You'll need an information security management system with a defined scope, risk assessment, chosen controls, responsibilities and evidence that the processes work.

Use the technical review to feed that work. For example, record the risk from unmanaged accounts, decide how it will be treated, assign an owner and keep evidence of the changes and ongoing checks. Don't promise a certification date until someone has assessed the wider gaps.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions