Solved

ISA Healthcheck

Posted on 2013-01-04
5
497 Views
Last Modified: 2013-01-22
1) What should/would/do external or internal IT auditors or security professionals look at when reviewing the configuration and management of a corporate ISA server? Could you provde some examples of essential things that should be looked at, common mistakes admins make, common issues found through "set it and forget it" type configs...

2) What sort of things would indicate a poorly configured/managed ISA server, please provide some practical examples for a manager/low tech, with subsequent risks....
0
Comment
Question by:pma111
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 18

Accepted Solution

by:
irweazelwallis earned 250 total points
ID: 38743561
depends how your ISA is used and setup
i.e. is it only out going as a User proxy
or is it used a reverse proxy
then is it externally facing or behind another firewall

Simple scenario - if behind another firewall and only used for user proxy and then a rule check to ensure there are no inbound rules and the outbound is only those required i.e. HTTP, HTTPS, FTP
Then a rule base check and permissions check (which users have access to which rules) which depends on your HR/Fair usage policy as to how through you are to ensure people can get to what they need to and anything else is blocked

Less simple
externally facing but only used for user proxy - a Penetration test would be appropriate, probably as part of a full external test along  with the checks above

Complicated - behind another firewall bit with both inbound and outbound rules
Along with the rule check on the ISA for outbound access a rule check for inbound and a Pen Test for all externally accessible services

then the final scenario is externally presented and both inbound and outbound rules - this would be the same as the check above
0
 
LVL 18

Expert Comment

by:irweazelwallis
ID: 38743572
Common mistakes
User Proxy (outbound)
fairly open rules i.e. Any<>Any style rules meaning any users can get to and from any destinations
use of individuals instead of groups to allow access to rules
combining rules where additional rules should be used, allow access to additional sites.

All these come from initial setup or poor change control, making sure this is all documented with what rules should be on there and standards for creating rules will help avoid these situations

The risk is that users can get to sites that they should be allowed to get to from a corporate stance i.e. facebook, twitter etc
or
they can get to sites that will damage the company or its infrastructure i.e. downloading malware, viruses etc

Risks for outbound rules is that internally services are presented to users that should have access to them i.e. hackers that could gain access to your network.
this is either through incorrectly configured rules or by poor patching which leaves systems with vulnerabilities
0
 
LVL 3

Author Comment

by:pma111
ID: 38743587
Thank you:

>>combining rules where additional rules should be used, allow access to additional sites.
>>use of individuals instead of groups to allow access to rules

Can you elaborate on these a little?
0
 
LVL 18

Expert Comment

by:irweazelwallis
ID: 38743604
rule 1 - allows Group 1 access to Website list 1

you amend the rule to allow group 1 access to website list 2

someone then asks to have access to website list 1 but doesn't/shouldn't need access to webste list 2

they are just added into rule 1 instead of creating rule 2
which would be - rule 2 allowings group 2 access to website list 1
0
 
LVL 5

Assisted Solution

by:balmasri
balmasri earned 250 total points
ID: 38745038
usually check the following:
-Administrative roles/permissions over the server , Array.
-Unnecessary Rules  like allow outbound any protocols.
-localhost (TMG server ) is allowed to access internet.
-services that are not necessary to be enabled such as print spooling, alert ...etc
-Checking for approvals for each rule created.
-security features such flood mitigation , IDS, ...etc.
-Logging is enabled.
-The reporting is healthy.
-The server is healthy : AV is installed, Local Admin PWD is complex ...etc.
* as a bottom line for auditors : if you have IT manager's approval for any exception even if allow any <->any , they will not write it down as a finding.
0

Featured Post

Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
Resolve DNS query failed errors for Exchange
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…
Finding and deleting duplicate (picture) files can be a time consuming task. My wife and I, our three kids and their families all share one dilemma: Managing our pictures. Between desktops, laptops, phones, tablets, and cameras; over the last decade…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question