ITA, HIDS, SCSP Comparison Document

Article:TECH114140  |  Created: 2008-01-26  |  Updated: 2009-01-06  |  Article URL http://www.symantec.com/docs/TECH114140
Article Type
Technical Solution


Problem






Solution



Symantec and the Symantec logo are U.S. registered trademarks of Symantec Corporation. Other brands and products are trademarks of their respective holder/s. Copyright © 2005 Symantec Corporation. All rights reserved. Printed in the U.S.A. 11/05 All product information is subject to change.
Symantec Critical System Protection 5.0 overview and feature comparison with Symantec Host IDS 4.1.1 & Intruder Alert 3.6.1

November 2005

Purpose:

This document assists in explaining the differences between Symantec Host IDS, Symantec Intruder Alert and their recent upgrade called Symantec Critical System Protection 5.0. The document contains three sections. The first section outlines the differences between the solutions. Section two provides an overview of the out of the box intrusion prevention policies for SCSP 5.0. Section three provides an overview of the out of the box detection policies included in SCSP 5.0.

Audience:

The audience for this document is the security architect, security analyst or IT manager responsible for server based intrusion prevention as well as system monitoring & auditing. This document is specifically written for existing Symantec Host IDS or Intruder Alert customers who are reviewing the opportunity to upgrade to Symantec Critical System Protection 5.0.

Section 1 – understanding the differences

This section outlines the functionality differences between the two solutions. For the most part, Symantec Critical System Protection 5.0 is a super-set of the Symantec Host IDS and Intruder Alert solutions. Symantec Critical System Protection leverages the high value functionality from Symantec Host IDS and incorporates an entirely new set of functionality that protects serves from day zero threats and provides enterprise wide proactive security policy enforcement.

(Note: The light yellow boxes denote an advantage for Symantec Critical System Protection 5.0)

Feature DescriptionSymantec Host IDS 4.1.1Intruder Alert
3.6.1
Symantec Critical System Protection 5.0
Intrusion Prevention
1Process Monitor – watch critical processes, restart based upon policy (this was a Host IDS specific function) YesNoThe IPS component proactively protects critical processes from being terminated by validating system calls against security policy. The system monitoring component can watch for process termination and can restart or alert.
2Process Blocker – blocks processes from starting (this was a Host IDS specific function)YesNoPrevents new processes from starting by validating system calls against security policy
3Process Reporter – a complete view of processes running on the system (snapshot – this was a Host IDS specific function) YesNoNo snapshot of processes is provided in SCSP.
4Exploit preventionNoNoUtilizes behavior control descriptors for O/S functions, services and applications. These descriptors define acceptable behavior and prevent hijacking by security risks. Any attempt by system services, applications or users to access system resources that is not acceptable will be automatically blocked and logged. Exploit prevention is automated through the use of “out of the box” policies. See section 2 for more details. Exploit prevention does not have to be implemented. But if it is implemented, it may operate in audit (prevention disabled) mode or enforcement mode.
5Application profiling toolNoNoIncludes an application profiling tool to enable administrators to create a baseline behavior control descriptor for legacy applications or other applications that may not be included in the Symantec policy library
6Restricts application usage of network resourcesNoNoRestricts applications and services to their known good network activity. This prevents exploits from taking advantage of an application and forcing it to use the network in malicious ways
7Prevents registry changesNo – HIDS has registry watchNoLocks down the registry (or sections of the registry) to prevent modification. This assists in stopping unknown attacks that leverage registry setting changes as one of their attack vectors.
8Executable white listingYesNoExplicitly defines the set of applications and services that may execute on the endpoint. This allows administrators to create hardened systems that perform limited functionality to reduce the risk of exposure.
9Executable black listingYesYesExplicitly defines the set of applications and services that may NOT execute on an endpoint. This allows administrators to proactively enforce policy across the enterprise and ensure that unwanted applications do not reside on any servers. (for example prevent the running of P2P file sharing programs or multi-player game software)
10Active protection of system configurationNoNoExplicitly protects system configuration settings. This protection will prevent any user from tampering with or changing system settings no matter the level of user credentials.
11Active protection of system resourcesNoNoExplicitly protects system resources such as the registry, file systems and even default printers. This protection will prevent any user from tampering with or changing system settings no matter the level of user credentials.
12MS Windows buffer overflow protectionNoNoDetects and stops the execution of buffer overflow threats that exploit the operating system. (Symantec also has a separate memory firewall solution available to augment the buffer overflow protection provided by Symantec Critical System Protection)
13Default O/S & interactive protection policiesNoNoDefault policies are listed in section 2. By providing out of the box systems can be protected upon initial installation
14Device controlsNoNoPrevents the use of (either reading or writing to/from) USB devices, removable media, drive mounting, Bluetooth devices, etc based upon policy
15Server firewall NoNoServer firewall monitors incoming and outgoing traffic, blocks ports and protocols based upon policy.
16Policy enforcementNoNoEnforces security policy across the enterprise without requiring reconfigurations at each end point. Global policy enforcement can reduce the impact of configuration errors and reduce the amount of time required to enforce policy compliance.
System Monitoring
17File watchYesNoYes
18Audit log trackingYesYesYes
19Custom log trackingYesYesYes
20Customizable intrusion detection policies and responsesYesYesYes
21Smart event responseYesYesYes
22Threshold based alertingYesNoYes
23System monitoring policy library YesYesYes
24Global flags and timersYesYesNo
25Bulk log transfersNoNoProvides the administrator with the ability to bulk transfer the security event log to the central management server.
26Tamper resistant log filesNoNoLog files are fingerprinted via a check sum and then securely transmitted to prevent tampering.
Centralized Reporting & Alerting
27Customizable rule setsYesYesYes
28ReportingYesYesYes
29Predefined queries & custom queriesNoNoYes
30Integrated with Symantec Security Information ManagerYesYesYes
31Alerting – EmailYesYesYes
32Alerting – SNMPYesYesYes
33Alert management consoleYesYesYes
34DeepSight Threatcon integrationNoNoSymantec DeepSight Threatcon information is integrated into the home page of the management interface. This allows administrators to keep up to date on the Theatcon level and provides links to important information about current threats.
Platform Support
35Windows 2000YesYesYes
36Windows NTYesYesYes
37Windows XPYesYesYes
38Windows 2003 EEYesYesYes
39Solaris 8 SPARCYesYesYes
40Solaris 9 SPARCYesYesYes
41HP/UX 11iYesYesMonitoring & Auditing (IDS) only in 5.0
42HP/UX 11i v2YesYesMonitoring & Auditing (IDS) only in 5.0
43AIX 5.2 & 5.3Yes + AIX 5.1YesMonitoring & Auditing (IDS) only in 5.0
44Redhat Linux ES 3YesYes1st half 2006
45Redhat Linux 7.3YesYes1st half 2006
46SuSE Linux Enterprise Server 8NoNo1st half 2006
47SuSE Linux Professional 9NoNo1st half 2006
48IBM DB2YesNoNo
49Microsoft SQL ServerNoNoYes
50Management Server language variation U.S. EnglishU.S. EnglishU.S. English
51Agent platform language variations U.S. EnglishU.S. EnglishU.S English
52SESA Management ConsoleYesNoNo, utilizes SESA collector at the management server (not the agent) to integrate with the Symantec Security Information manager 4.0
    Section 2 – Overview of the “Out of the Box” prevention policies for Windows & UNIX

    Windows Prevention Policy LibrarySymantec Host IDS/Intruder AlertFor full detection policy details, please see document titled “Symantec Critical System Protection Prevention Policy Reference Guide”
    53Windows NULL Policy YesAllows all processes to perform all functions
    54Windows Core OS Policy NoProvides general integrity protection. Includes protection for processes and shared libraries that are loaded without user intervention. Confines many of the system services and applications to acceptable behavior. Policy limits the ability of a service or application to harm the integrity of the system or O/S. Policy is configurable.
    55Windows Strict OS Policy NoProvides all of the protection of the core policy plus adds restrictions for interactive programs including blocking (admin can create white lists of acceptable programs) Also by default blocks changing of screen saver, blocks com object registration and ActiveX component installation, blocks changing of network services (such as DNS), blocks changing of default printer and blocks recognition of Bluetooth devices. Policy is configurable.
    56Windows Limited Execution Policy NoBlocks the execution of all interactive programs except those listed by the administrator as approved applications. Suitable for dedicated workstations with a small set of applications that require a high level of control. (for example, a kiosk or an appliance like server)
    57Default protection policies for Microsoft IIS, Exchange, SQL Server, Outlook and OfficeNoYes – see prevention policy reference guide for more detailed information
    Unix Prevention Policy Library
    58Solaris Standard PolicyNoProvides a general integrity protection policy. It confines many of the operating system daemons that have been identified as vulnerable as well as some common applications.
    59Solaris NULL PolicyNoAllows all processes to perform all functions
    60Apache PolicyNoYes – see prevention policy reference guide for more detailed information
    61Sendmail PolicyNoYes – see prevention policy reference guide for more detailed information
    62Postfix PolicyNoYes – see prevention policy reference guide for more detailed information
    63Linux Standard Policy NoProvides a general integrity protection policy. It confines many of the operating system daemons that have been identified as vulnerable as well as some common applications.

    Section 3 – Overview of the “Out of the Box” detection policies for Windows & UNIX

    Windows Detection Policy LibrarySymantec Host IDS/Intruder AlertFor full detection policy details, please see document titled “Symantec Critical System Protection Detection Policy Reference Guide”
    65Domain Trust Configuration – detects a creation or removal of a trusted domain configurationYesYes
    66Agent Status – Monitors the status of SCSP at the endpointYesYes – In addition, can proactively prevent the shutdown of its agent processes
    67File Tampering – detects changes to critical system filesYesYes – In addition, can lock down system files and prevent write access so that files may not be modified
    68ISS scanner probe – detects a heavy probeYesYes
    69Malware – detects the effects of malicious applications on the Windows system – signatures identify 12 common known exploitsYesYes – In addition, can automatically prevent known and unknown exploits from gaining a foothold into the system by restricting applications & services to known good behaviors. This prevents multi-vector attacks from hijacking a system service and forcing it to do alternative tasks.
    70Microsoft Front Page activity – detects requests made to the front page serverYesYes, In addition can proactively prevent Microsoft Front Page activity based upon security policy
    71Microsoft IIS Security Configuration – detects changes to IIS security settingsYesYes – In addition, can proactively prevent changes across the enterprise.
    72Microsoft IIS vulnerable CGI scripts – detects web access to vulnerable CGI scripts YesYes
    73Network communication configuration – detects changes to settings that impact network communicationsYesYes – In addition, can prevent changes to system configuration settings
    74Symantec AntiVirus client communication – detects alerts from Symantec AntivirusYesYes
    75Sans – Detects Microsoft Windows issues from the SANS Top 20 listYesYes – In addition, can proactively enforce security policy across the enterprise according the recommendations of SANS (for example, disable IIS on all servers that don’t require it – After defined in policy, SCSP could prevent IIS from running on any server without having to re-configure every server)
    76System Audit Tampering – detects system audit changes and the clearing of audit logsYesYes – in addition, can proactively protect audit settings and prevent changes and clearing of audit logs based upon policy.
    77System Authentication Configuration – detects changes to Windows Active Directory authentication and encryption settingsYesYes
    78Autorun detection – detects if changes are made to the autorun which would execute code upon startup (such as a CD Rom) YesYes
    79Windows Failed Access – detects when a user has failed to authenticate either locally or via a domainYesYes
    80System file protection status – detects events by the Windows File Protection system which monitors critical system files which should remain available, detects file restorationsYesYes, In addition can proactively prevent system files from modification or deletion
    81System Group Management Changes – detects creating, enabling or changing of security groupsYesYes, In addition can proactively prevent the administrator from making changes
    82System Hardening – detects changes to user configured registry keys YesYes
    83System Logon Success – detects all successful local and remote Windows logonsYesYes
    84System remote logoff – detects all successful Windows logoffs. YesYes
    85System security configuration – detects changes to registry keys that impact security settingsYesYes, In addition can proactively prevent changes to registry keys
    86System Shares Configuration - detects the creation or removal of a shareYesYes, In addition can proactively prevent the creation or removal of a share
    87System Startstop Options – detects changes to system startup and shutdown settingsYesYes, In addition can proactively prevent the changes to system startup and shutdown settings
    88System User Configuration – detects changes made to user accountsYesYes, In addition can proactively prevent changes to user accounts
    89USB Device Activity – detects connection and disconnection of USB devicesYesYes, In addition can proactively prevent the use of USB drives as well as other removable media
    UNIX detection policy library
    90Apache Vulnerable CGI Scripts – detects activities of certain (59) vulnerable CGI scriptsYesYes, In addition can proactively prevent CGI scripts from executing
    91Agent Status – Monitors the status of SCSP at the endpointYesYes – In addition, can proactively prevent the shutdown of its agent processes
    92File Tampering – detects changes to critical system filesYesYes – In addition, can lock down system files and prevent write access so that files may not be modified
    93NetRecon – detects a scan by Symantec NetReconYesYes
    94Sans – Detects issues from the SANS Top 20 listYesYes – In addition, can proactively enforce security policy across the enterprise according the recommendations of SANS
    95Sendmail Brokenpipe messages – detects broken pipe error messagesYesYes, In addition has a default policy to protect Sendmail from exploitation. See intrusion prevention policy library.
    96Stack Execution Denied – detects attempts to execute instructions stored in the O/S stackYesYes
    97Syslogd tampering- detects when the syslog daemon isn’t runningYesYes
    98System Logon Failure – detects failed logon attempts from the local console or remote accessYesYes
    99System Logon Success – detects successful logon attempts from the local console or remote accessYesYes


Legacy ID



2008022610090353


Article URL http://www.symantec.com/docs/TECH114140


Terms of use for this information are found in Legal Notices