Windows Server Healthcheck

we have got audit number of windows 2008 servers critical controls, albeit not specific security (although undoubtedly there in top 15). database or file servers. audit more risk assessment/healthccheck, not audit can access in traditional sense of word.

i trying identify top 10-15 critical controls list servers can as possible in time available. patching, weak password identification etc 2 obvious security ones, don’t want purely focus on security settings.

the objective ensure servers have optimum availability, security/confidentiality, integrity, alignment vital controls , best practice. top 15 checks in expert opinion, i.e. important/vital. rather feedback rather being pointed guide.

hiya,

first of all, said, no guides - microsoft has provided tools scan of system on different levels, giving reports state areas needs attention based on own best practice. - quite useful in situation 1 describe.
(attack surface analyzer, microsoft security assessment tool, risk , health assessment program)

secondly define 15 important checks, rely heavily on scope, industry , role of servers. patching might not problem, if server role or industry doesn't point that.

in general need identify primary use of each server , critical data/process. how handle critical process.(access, storage, backup, memory, monitoring, resource trends etc.)

example:
database server based on microsoft sql.

- sql memory usage special, make sure min/max settings done.
- disk storage design reflects criticality of system (san, raid, backup etc.)
- limited amount of people has access server and/or databases.
- use service accounts services.
- insure personal accounts used. (no administrator accounts)
- insure sufficient patch/service pack level, corresponding criticality , usage of server.
- page file and/or memory dump file set accordingly.
- monitor resources (cpu, disk que etc.)
- port configuration done accordingly
- firewall configured properly
- ensure antivirus adressed, either need have or not have.
- firmware levels on associated hardware.
- single point of failures?
- bare metal recovery time/plan
- latest backup restore test. (if backup applicable)

hope serve inspiration :)

Windows Server  >  Windows Server General Forum