Endpoint Protection

 View Only
Expand all | Collapse all

Denial of service message

  • 1.  Denial of service message

    Posted Dec 10, 2009 07:42 AM
    Hello I closed teh other post to early I guess. If a user gets the

    denial of service is logged

    Then the client is beeing attacked from the outside is that right?

    The client I am working for is saying IPS is not seup to examine out-bound packets they think

    what should be the process when getting this type of message on a machine?


  • 2.  RE: Denial of service message

    Posted Dec 10, 2009 07:57 AM
    We get phony DOS log entries from computers on our OWN network.
    Apparently SEP believes that things coming from our remote offices to the DCs are DOS packets and blocks them.
    So far, the case has not yielded any solution or reason.
    What's happening in OUR case is this - clients that connect to our network through a Cisco ASA5505 are seen as attacking our DC servers, HOWEVER, Cisco says the packets are normal - they see no such attacks. AND, these are our own machines. Exactly identical in every single way to computers here in the home office with SEP never sees as attacking our DCs.
    And in fact, we've never ever in a whole year seen a DOS attack against us - except when SEP says our own computers are attacking us.
    SO, check the logs - check the source and destination IP addresses, MAC addresses, etc.  That is what the process should be. IF IT'S REAL, SEP will block the offending packets and you really need to do little more, IMO. But do check the logs for DETAILS.
    A TRUE DOS attack lasts for more than just a packet or two.......... and will indeed come from the outside. Check the details.


  • 3.  RE: Denial of service message

    Posted Dec 10, 2009 08:12 AM
    If you want to find which pc is sending packets to your the  Risk Tracer shold be enabled
    Below article will give a nice picture about this feature
    Worms and threats that spread across networks by network shares have become more common in recent years.--Like Downadup/Conficker


  • 4.  RE: Denial of service message

    Posted Dec 10, 2009 08:14 AM
    what log shoudl I request from the client, or from the database to review?


  • 5.  RE: Denial of service message

    Posted Dec 10, 2009 08:26 AM
    do I just request the

    seclog.log --IPS security Log

    or shoudl I do something from SEPM instead? thanks guys


  • 6.  RE: Denial of service message

    Posted Dec 10, 2009 08:55 AM
    You can find out it from SEPM (I think this is easy). You can fin same information from traffic log from the client also... 
    Pls read carefully the article which is present in my earlier post..


  • 7.  RE: Denial of service message

    Posted Dec 10, 2009 08:59 AM
    ok i wil going to request the seclog.log and go from there i will post back thanks guys


  • 8.  RE: Denial of service message

    Posted Dec 10, 2009 09:05 AM
     I think this information is present in tralog.log


  • 9.  RE: Denial of service message

    Posted Dec 10, 2009 11:14 AM
    The IPS rule that defines DOS attacks is hard coded in such a way that any burst of traffic from any given IP address will trigger it.


  • 10.  RE: Denial of service message

    Posted Dec 10, 2009 11:29 AM
    Yes, but in our case, it's phoney.
    There is no such burst, it's seeing the packets ONLY from certain computers behind our firewalls/ASAs as attackers - and it's actually flagging them as LARGER than normal packets and determining it as a DOS because it is seeing LARGE packets.
    There are no such packets coming in according to Cisco!
    So we're working a case (albiet VERY slowly) to find out why SEP is flagging ONLY a few computers ONLY behind an ASA as sending packets that are too big - when they are not.....


  • 11.  RE: Denial of service message
    Best Answer

    Posted Dec 10, 2009 11:59 AM
    yes view the ports analyse the IP's and you need to determin if it is False postive or a real attack..
    In some cases if you have monitoring server it also causes false dos alerts..in that case you might need to create exceptions for these IP addresses.