Search

  • Advertisement Filtering Blocking

    We migraded from surfcontrol to websense 7.6 and I am currently working to make the case to management to block advertisements because they ad little or no value to business, are a key source of malware, and utilize considerable bandwidth. After reading several forums about headaches associated with blocking ads, see Fox News Video thread http://community.websense.com/forums/p/2564/9127.aspx#9127 , along with a call from users testing this feature after following a link related to black Friday specials
    Posted to General (Forum) by SecSam on 27 Oct 2011
    Filed under: advertisements
  • Re: Blocking Advertisements stops FoxNews Videos

    I was wondering if you are still blocking advertisements and if it is still a management nightmare. I am the only admin in a govt agency and was hoping to block ads but I am concerned about going down this road even though it seems like a prudent security related approach. I opened a post called Advertisement Filtering and asked for feedback on this from WebSense Customers. Thanks for your
    Posted to Managing Policies for Clients (Forum) by SecSam on 27 Oct 2011
  • Re: Category Filtering and Blocking

    Thanks for the feedback. With the help of WebSense support I was able to get over this hurdle. Here is a short synopsis. The problem was ultimately resolved by hard coding the mac address of the gateway into the config.xml file. By running the command arp -a we could get this information. C:\Program Files (x86)\Websense\Web Security\bin>arp -a Interface: 10.10.10.80 --- 0xe Internet Address Physical Address Type 10.10.10.1 00-00-00-00-00-01 dynamic 10.10.10.3 00-0--00-00-00-02 dynamic 10.10.10
  • Category Filtering and Blocking

    I have had WS 7.6 standalone running for a week in monitor mode. Today I configured a new policy with new category and protocol filters. I assigned this policy to the IP address of a test machine. When test pc browses to a gambling site I am not blocked but WS says it is/was blocked. I browsed the forums and guides- Placed the monitoring nic in promiscuous mode and even tried adding the IP of the server to the eimserver.ini. with no help. One thing I saw reference to was the browser service needs
  • Re: Websense not filtering entire IP range

    Thanks for the reply. Since the policy was applied to an IP I was thinking that maybe order of precedence was the issue. I thought IP would take precedence over the user but maybe I had that wrong. To be sure assigned the User directly to the same policy and ran testlogserver agiain. time= Tue Aug 30 14:18:01 2011 version= 5 server= 10.20.161.xx source= 10.20.xx URL= www.flalottery.com protocol= 1 - http port= 80 networkDirection= Inbound method= contentType = category= 13 - GAMBLING categoryReason
    Posted to Configuration and Settings (Forum) by SecSam on 30 Aug 2011
  • Re: Category Filtering and Blocking

    Since I applied the policy to an IP I was thinking that maybe order of precedence was the issue. I thought IP would take precedence over the user but maybe I had that wrong. To be sure I also assigned the User directly to the same policy and ran testlogserver agiain. time= Tue Aug 30 14:18:01 2011 version= 5 server= 10.20.161.xx source= 10.20.xx URL= www.flalottery.com protocol= 1 - http port= 80 networkDirection= Inbound method= contentType = category= 13 - GAMBLING categoryReason= 0 - CatNone disposition
  • Re: To SPAN to Integrate? Opinions Needed!

    We are on CheckPoint version 7.0 and since we are going to be migrating from SurfControl I was planning to go with Web security 7.5, which apparenty does support Checkpoint version 7.0
  • Re: To SPAN to Integrate? Opinions Needed!

    I too am planning to migrate from surfcontrol to WebSense Security with a CheckPoint. I was hoping to be able to increase our coverage of other DMZ's by integrating port 80 filtering with the CheckPoint and then hanging network agent off of a monitoring port to capture other protocol traffic. We have a nifty device that can aggregate traffic from multiple dmz's and filter out the port 80 traffic going to the monitoring port reducing the overhead. While I am in favor of this my management
Page 1 of 1 (8 items) | More Search Options