Can I safely use CyberHawk with PG

Discussion in 'ProcessGuard' started by one111, Nov 9, 2006.

Thread Status:
Not open for further replies.
  1. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    And more importantly, CyberHawk wants to modify Explorere exe and Winlogon
    exe. In the meanwhile PG is preventing this change. Should I allow it?
     
  2. aigle

    aigle Registered Member

    Joined:
    Dec 14, 2005
    Posts:
    11,047
    Location:
    Saudi Arabia/ Pakistan
    U should in my opinion.
     
  3. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    Thank you

    I see form your resume (arsenal) that you have experience in the matter (-;
     
  4. aigle

    aigle Registered Member

    Joined:
    Dec 14, 2005
    Posts:
    11,047
    Location:
    Saudi Arabia/ Pakistan
    I am not experienced! BUt its, a general rule to give full privilages to any security software on ur system unless u know very details of them and OS. bTW I never used PG and CH together, so u have to try and see. May be some other have done it.

    BTW, u have made two post on same matter. I will suggest u to make one post and wait for replies.
     
  5. one111

    one111 Registered Member

    Joined:
    Apr 6, 2005
    Posts:
    92
    This is the official reply I received from CyberHawk:

    We can't provide many specific technical details due to the proprietary nature of how Cyberhawk protects, but the basics are that in order for Cyberhawk to protect you it constantly monitors your entire system for any signs of malware behavior. It does so in an extremely intelligent way, and in ways that allow it to detect threats that other applications miss.

    Certain types of threats, such as rootkits, require our very careful examination of processes such as Winlogon and Explorer.exe. This “modification” you are seeing should be seen as a legitimate action for Cyberhawk to do in order to help track down certain types of threats like rootkits.

    Becky Dubrow
     
Thread Status:
Not open for further replies.