Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: blocking thru IE |
|---|---|
| Date: | Mon, 9 Apr 2007 14:07:49 -0500 |
Can AD push information down to the IE Content Advisor? It would be nice to implement this from AD on an as needed basis... Ernest E. Busby II Information Security Analyst TWC -----Original Message----- From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com] On Behalf Of mcclenbw@oneonta.edu Sent: Monday, April 09, 2007 12:57 PM To: Jim Harrison; Rocky; focus-ms@securityfocus.com Subject: RE: blocking thru IE If there are a multitude of sites and clients, then yes, something like ISA might be the way to go. If you are talking about one site on a given client, or even account/profile, keep it simple and cheap and use the content advisor. I've seen the content advisor used at a previous job where if a user hadn't activated their account already, they would log in with the "newuser" account and they were restricted to only be able to run IE and the content advisor only allowed them to go to the account activate site. In this situation, something like ISA is overkill. Heck, in this case the cost and overhead of ISA probably would have killed the project. Brady McClenon Administrative Computer Services State University College at Oneonta Oneonta, NY 13820
-----Original Message----- From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com] On Behalf Of Jim Harrison Sent: Monday, April 09, 2007 12:26 PM To: Rocky; focus-ms@securityfocus.com Subject: RE: blocking thru IE Rather than trying to control it at the client (where the user can potentially disable your tweaks), exercise this control at the edge. Whether you use ISA, Checkpoint, Pix, BlueCoat, Juniper or WinGate,
the
process is basically the same. 1. Determine where that web site lives. This can be difficult if its hosted by one of the "big kids", like Akamai, since they use a globally-dispersed, short-lived RR-name scheme (20 sec TTL). 2. Block those requests by name and IP at the edge. -----Original Message----- From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com] On Behalf Of Rocky Sent: Friday, April 06, 2007 10:49 AM To: focus-ms@securityfocus.com Subject: blocking thru IE Hey guys, is there a way to block everything on IE6 or Firefox 2.0 and
just permit one website? i'm playing with IE content but i just can't get it done. thanks a lot. rocky All mail to and from this domain is GFI-scanned.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: blocking thru IE, amabes |
|---|---|
| Next by Date: | RE: Running commands on workstations from domain controller, Weir, Jason |
| Previous by Thread: | RE: blocking thru IE, mcclenbw |
| Next by Thread: | RE: blocking thru IE, amabes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |