in

eEye Digital Security

The endpoint to vulnerability starts here.

 

Vulnerability Scanner - Registry Settings for RasMan Not Detected

Last post 10-09-2009 8:29 PM by Blue1978. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 10-09-2009 4:46 PM

    Vulnerability Scanner - Registry Settings for RasMan Not Detected

    Vulnerability scanner doesn't properly detect registry settings for MS RAS Logging, MS RAS Encrypt, MSCHAPv2 VPN, PPP Client Security, as shown below. This is the case on 2 computers that use Blink.
    (a) Registry access is granted; all other app or registry changes (except NtfsDisable8dot3NameCreation--see post) are detected by the scanner.
    (b) Services for RasMan, RasAuto, Remote Desktop are disabled.
    (c) No malware.

    Enabling services, removing reg entries/re-entering, reboot, removing/reinstalling Blink, _etc_ are not a fix. 

    When using the free edition or the purchased install version, Blink Personal Version 4.3.2, Vulnerability Scanner Version 5.10.1, Audits version 2115--if RasMan etc is audited--no vulnerabilities shown for RasMan etc. 

    Any help appreciated. Thank you.
     
    OS: XP,SP3
    Blink Personal Version 4.4.2, Rule version 1543
    AntiVirus Version 1.0.797
    Vulnerability Scanner version 5.10.15, Audits version 2144

    MS RAS Logging
    How To Fix To enable logging, set the following Registry key settings: Hive: HKEY_LOCAL_MACHINE Path: System\CurrentControlSet\Services\Rasman\Parameters Key: Logging Type: REG_DWORD Value: 1

    MSCHAPv2 VPN
    How To Fix To enforce MSCHAP V2 set the following key: Hive: HKEY_LOCAL_MACHINE Path: System\CurrentControlSet\Services\RasMan\PPP Key: SecureVPN Type: REG_DWORD Value: 1
     
    MS RAS Encrypt 
    How To Fix To force encrypted transfers set the following Registry key settings:
    Hive: HKEY_LOCAL_MACHINE
    Path: System\CurrentControlSet\Services\RASMAN\PPP
    Key: ForceEncryptedData
    Type: REG_DWORD
    Value: 1
     
    PPP Client Security
    How To Fix To require authentication set the following key:
    Hive: HKEY_LOCAL_MACHINE
    Path: System\CurrentControlSet\Services\Rasman\PPP
    Key: ForceEncryptedPassword
    Type: REG_DWORD
    Value: 2

  • 10-09-2009 6:16 PM In reply to

    Re: Vulnerability Scanner - Registry Settings for RasMan Not Detected

    If I remember correctly, some of these registry entries (if they did not exist initially) you had to manually enter in the keys.  Was this the case?  I have not used XP for awhile now, but I kinda of remember these alerts from when I did.

  • 10-09-2009 8:08 PM In reply to

    Re: Vulnerability Scanner - Registry Settings for RasMan Not Detected

    Yes, manually entered, but as I wrote above, alerts not detected in free version nor in initial install version. On one machine, the settings as shown, were done prior to using any version of Blink. Any solution please?

  • 10-09-2009 8:29 PM In reply to

    Re: Vulnerability Scanner - Registry Settings for RasMan Not Detected

    Brian,

         Do you know how to correct this issue the user is experiencing?

     

Page 1 of 1 (4 items)
© 1995 - 2009 eEye Incorporated