Endpoint Protection

 View Only
Expand all | Collapse all

Unexpected result from Tamper protection

pete

peteMar 07, 2013 01:04 AM

  • 1.  Unexpected result from Tamper protection

    Posted Mar 07, 2013 01:00 AM

    Hi All,

    Good Day..

    We are using Sep 12.1 RU1 MP1 on a windows Architecture, and some if our  clients we notice that even Tamper protection is enabled (action is block and log, padlock also locked) we are able to edit registry? And could not see anything on Tamper protection log regarding this.

    Mean while SCCM is collecting info about SEP, then it is getting blocked and logged (looks Tamper Protection is working )

    Any idea’s why this mismatch?

    Best Regards

    Ajin



  • 2.  RE: Unexpected result from Tamper protection

    Broadcom Employee
    Posted Mar 07, 2013 01:04 AM

    what registry value was changed?

     



  • 3.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 01:17 AM

    Hi Pete,

    Thanks for your inputs.

    Value of mycomputer\HKEY_LOCAL_MACHINES\SOFTWARE\Symantec\Liveupdate\Preferences\ All Transports Available from 0 to 1

     And I am able to create a new key any where under  mycomputer\HKEY_LOCAL_MACHINES\SOFTWARE\Symantec

     

    Regards

    Ajin



  • 4.  RE: Unexpected result from Tamper protection

    Broadcom Employee
    Posted Mar 07, 2013 01:29 AM

    since you say the client is RU1 MP1, this should not been seen.

    Tamper Protection exceptions are not honored
    Fix ID: 2580578
    Symptom: Tamper Protection exceptions are not honored. An excluded process will trigger tamper protection.
    Solution: The SEP client was sending a delta of the exclusion list to the BASH component. The client was modified to send the complete list to resolve this issue.
     
    can you check if RU2 client still has the issue,


  • 5.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 01:35 AM

    Hi Pete,

    Thanks again.

    If it is a bug we can try on RU2, but we cannot deploy RU2 with immediate effect on all clients since it requires lot of POC / Approvals and we are operating this solution across Globe.

    I will come back with the results after testing on a test bed.

    SEPM will be same 12.1 RU1 MP1 and client will be RU 2 does it sounds good?

    Regards

    Ajin



  • 6.  RE: Unexpected result from Tamper protection

    Broadcom Employee
    Posted Mar 07, 2013 02:17 AM

    yep should not be any issue, but as a best practise the SPEM has to be the same version or higher version than that of clients.

    this is only for test and let know the outcome.

     



  • 7.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 03:10 AM

    Can you try if on the same machine you can as well change any other existing entries? (just to exclude the possibility some of the keys are not covered by TP). Take for example the one for SEP debug:

    1. Navigate to:  HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC
    2. Double-click smc_debuglog_on
    3. Change the Value data to and click OK

     

    + just to check if the Tamper Protection shows as well enabled status in the SEP client GUI itself?



  • 8.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 05:18 AM

    Hi Pete,

    Here we go.

    Test Bed OS Window 7 Ent 64 Bit with Sep 12.1.2

    We have done that tested on SEP 12.1.2 and i am able to modify computer\HKEY_LOCAL_MACHINES\SOFTWARE\Won6432Node\Symantec\Liveupdate\Preferances value from 1to 0.

    Since it is also a Symantec Endpoint Related Registry

    And registry values under computer\HKEY_LOCAL_MACHINES\SOFTWARE\Symantec\Symantec Endpoint Protection  i am not able to change .

    From Client UI Tamper Protection is enabled

    Please have a look

    Regards

    Ajin



  • 9.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 05:26 AM

    Hi Sebastian

    Thanks for your inputs.

    I have tested the same on a Test bed 12.1.2 over windows 7 .

    I am able to modify computer\HKEY_LOCAL_MACHINES\SOFTWARE\Won6432Node\Symantec\Liveupdate\Preferances value from 1to 0.

    Since it is also a Symantec Endpoint Related Registry

    And registry values under computer\HKEY_LOCAL_MACHINES\SOFTWARE\Symantec\Symantec Endpoint Protection  i am not able to change .

    From Client UI Tamper Protection is enabled

    Regards

    Ajin



  • 10.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 05:41 AM

    It would seem then the Tamper Protections does not necesserily blocks access to all of the SEP registry keys - for sure what I know the SEP system registry keys would be blocked from tampering. Other preferences keys or such may have been left alone and available for changing.



  • 11.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 05:53 AM

    Hi Sebastian

    It looks like a Bug / product is designed to work so ?

    Regards

    Ajin



  • 12.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 05:57 AM

    AFAIK Tamper protection was used to protect Symatnec processes. There were few registry tweaks which were used to uninstall SEP without password. To protect that Symantec now prohibits registry modification of Symantec endpoint folder. Thats why you are able to modify the Livupdate settings.

    However if you try to kill Liveupdate from task manager it will say access denied. Its related to only Symantec processs ( .exe files) Plus Symantec endpoint registry alone.

     

     



  • 13.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 06:05 AM

    Hi Rafeeq,

    Thanks for your inputs.

    so user is allowed to change theses settings via registry, is there any other method to Prevent this ? from SEPM side

    Regards

    Ajin



  • 14.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 06:11 AM

    You should be able to prevent it easily from OS side - GPO for example or access rights to registry keys. But not sure SEPM offers here any other possibilities



  • 15.  RE: Unexpected result from Tamper protection
    Best Answer

    Posted Mar 07, 2013 06:18 AM

    Hi Sebastian

    Thanks for your inputs

    GPO  is a good option . so can we conclude this as below

    “As Of now Tamper Protections does not necessarily blocks access to the entire SEP registry keys the SEP system registry keys would be blocked from tampering. Other preferences keys or such may have been left alone and available for changing

    Regards

    Ajin



  • 16.  RE: Unexpected result from Tamper protection

    Posted Mar 07, 2013 06:19 AM

    Not possible from SEP as sebastin said you can always use GPO.

    Moreover even if you change LU settings in registry those will be reverted back once the client communicates with Manager.