Comodo DM Admin Guide

Comodo Device Manager - Administrator Guide

•

To edit or delete the component, click More Actions and choose the option.

The saved 'Viruscope' settings screen will be displayed with options to edit the settings or delete the section. Refer to the section

' Editing Configuration Profiles ' for more details.

6.1.3.1.6. HIPS Settings

The Host Intrusion Prevention System (HIPS) constantly monitors system activity and only allows executables and processes to run if they comply with security rules that have been enforced by the Windows profile applied to the managed computer.

Comodo Endpoint Security ships with a default HIPS ruleset that works 'out of the box' - providing extremely high levels of protection without any user intervention. For example, HIPS automatically protects system-critical files, folders and registry keys to prevent unauthorized modifications by malicious programs. Administrators looking to take a firmer grip on their security posture can quickly create custom policies and rulesets using the powerful rules interface and roll it out through the Windows profile.

To configure HIPS Settings and Rules

•

Click 'HIPS' from the 'Add' drop-down

The HIPS settings screen will be displayed. It contains six tabs:

•

HIPS Settings - Allows you to configure the settings that govern the overall behavior of the HIPS component.

•

HIPS Rules - Allows you to view, create and modify rules that determine how the applications in the managed

computer have to be protected

•

Rulesets - Allows you view predefined rulesets and create new rulesets that can be applied to the applications on the

managed computer.

•

Protected Objects - Allows you to view and edit predefined 'Registry Groups' and 'COM Groups', create new groups so

as to add them to Protected Objects.

HIPS Settings

Comodo Device Manager - Administrator Guide | © 2016 Comodo Security Solutions Inc. | All rights reserved 303


The HIPS settings panel under the HIPS tab allows you to enable/disable HIPS, set HIPS security level and configure HIPS' general behavior.

Form Element

Enable HIPS

Hips Security Level

HIPS Settings - Table of Parameters

Description

Allows you to enable or disable HIPS protection for the managed computers to which the profile is applied. ( Default=Enabled)

If enabled, you can configure the HIPS security level and monitoring settings.

If HIPS is enbled, you can choose the security level for the HIPS to provide at the managed computer from the drop-down below 'Enable HIPS'.




Monitoring Settings

The available options are:

•

Paranoid Mode: This is the highest security level setting and means that HIPS monitors and controls all executable files apart from those that you have deemed safe.

Comodo Endpoint Security does not attempt to learn the behavior of any applications even those applications on the Comodo safe list and only uses your configuration settings to filter critical system activity. Similarly, the Comodo Endpoint Security does automatically create 'Allow' rules for any executables - although the end user still has the option to treat an application as 'Trusted' at the HIPS alert. Choosing this option generates the most amount of HIPS alerts and is recommended for advanced users that require complete awareness of activity on their system.

•

Safe Mode: While monitoring critical system activity, HIPS automatically learns the activity of executables and applications certified as 'Safe' by Comodo. It also

automatically creates 'Allow' rules for these activities, if the option ' Create rules for safe applications ' is selected. For non-certified, unknown, applications, the end-user will

receive an alert whenever that application attempts to run. Should you choose, the end-user can add that new application to the safe list by choosing 'Treat this application as a Trusted Application' at the alert. This instructs the HIPS not to generate an alert the next time it runs. If the endpoint is not new or known to be free of malware and other threats as in 'Clean PC Mode' then 'Safe Mode' is recommended setting for most users - combining the highest levels of security with an easy-tomanage number of HIPS alerts.

•

Clean PC Mode: From the time you set the setting to 'Clean PC Mode', HIPS learns the activities of the applications currently installed on the server while all new executables introduced to the server are monitored and controlled. This patentpending mode of operation is the recommended option on a new server or one that the user knows to be clean of malware and other threats. From this point onwards

HIPS alerts the user whenever a new, unrecognized application is being installed. In

this mode, the files with 'Unrecognized' rating in the 'File List ' are excluded from being

considered as clean and are monitored and controlled.

•

Training Mode: HIPS monitors and learn the activity of any and all executables and create automatic 'Allow' rules until the security level is adjusted. The end-user will not receive any HIPS alerts in 'Training Mode'. If you choose the 'Training Mode' setting, we advise that you are 100% sure that all applications and executables installed on teh endpoints are safe to run.

If HIPS is enbled, you can configure the activities, entities and objects that should monitored by it at the managed endpoint by clicking the 'Monitoring Settings' link.




Activities To Monitor:

•

Interprocess Memory Access - Malware programs use memory space modification to inject malicious code for numerous types of attacks. These include recording your keyboard strokes; modifying the behavior of applications and stealing data by sending confidential information from one process to another. One of the most serious aspects of memory-space breaches is the ability of the offending malware to take the identity of a compromised process to 'impersonate' the application under attack. This makes life harder for traditional virus scanning software and intrusion-detection systems.

Leave this option selected, and HIPS generates alerts when an application attempts to modify the memory space allocated to another application

(Default = Enabled).

•

Windows/WinEvent Hooks - In the Microsoft Windows® operating system, a hook is a mechanism by which a function can intercept events before they reach an application.

Example intercepted events include messages, mouse actions and keystrokes. Hooks can react to these events and, in some cases, modify or discard them. Originally developed to allow legitimate software developers to develop more powerful and useful applications, hooks have also been exploited by hackers to create more powerful malware. Examples include malware that can record every stroke on your keyboard; record your mouse movements; monitor and modify all messages on your computer and take remote control of your computer. Leaving this option selected means that an alert is generated every time a hook is executed by an untrusted application


•

Device Driver Installations - Device drivers are small programs that allow applications and/or operating systems to interact with hardware devices on the managed computer. Hardware devices include your disk drives, graphics card, wireless and




LAN network cards, CPU, mouse, USB devices, monitor, DVD player etc.. Even the installation of a perfectly well-intentioned device driver can lead to system instability if it conflicts with other drivers on the system. The installation of a malicious driver could, obviously, cause irreparable damage to the computer or even pass control of that device to a hacker. Leaving this option selected means HIPS generates alerts every time a device driver is installed on the computer by an untrusted application (Default =

Enabled).

•

Processes' Terminations - A process is a running instance of a program. Terminating a process, obviously, terminates the program. Viruses and Trojan horses often try to shut down the processes of any security software you have been running in order to bypass it. With this setting enabled, HIPS monitors and generates alerts for all attempts by an untrusted application to close down another application (Default =

Enabled).

•

Process Execution - Malware such as rootkits and key-loggers often execute as background processes. With this setting enabled, HIPS monitors and generates alerts whenever a process is invoked by an untrusted application. (Default = Enabled).

•

Windows Messages - This setting means Comodo Endpoint Security monitors and detects if one application attempts to send special Windows Messages to modify the behavior of another application (e.g. by using the WM_PASTE command)

(Default =

Enabled).

•

DNS/RPC Client Service - This setting generates alerts if an application attempts to access the 'Windows DNS service' - possibly in order to launch a DNS recursion attack. A DNS recursion attack is a type of Distributed Denial of Service attack whereby a malicious entity sends several thousand spoofed requests to a DNS server.

The requests are spoofed in that they appear to come from the target or 'victim' server but in fact come from different sources - often a network of 'zombie' computers which send out the requests without the owners knowledge. The DNS servers are tricked into sending all their replies to the victim server - overwhelming it with requests and causing it to crash. Leaving this setting enabled prevents malware from using the DNS

Client Service to launch such an attack


Objects To Monitor Against Modifications:

•

Protected COM Interfaces enables monitoring of COM interfaces you specified

from the COM Protection pane.

(Default = Enabled)

•

Protected Registry Keys enables monitoring of Registry keys you specified from

the Registry Protection pane.


•

Protected Files/Folders enables monitoring of files and folders you specified from

the File Protection pane.


Objects To Monitor Against Direct Access:

Determines whether or not Comodo Endpoint Security should monitor access to system critical objects on the managed computer. Using direct access methods, malicious applications can obtain data from a storage devices, modify or infect other executable software, record keystrokes and more. Comodo advises the average user to leave these settings enabled:

•

Physical Memory: Monitors your computer's memory for direct access by an applications and processes. Malicious programs attempt to access physical memory to run a wide range of exploits - the most famous being the 'Buffer Overflow' exploit.

Buffer overruns occur when an interface designed to store a certain amount of data at a specific address in memory allows a malicious process to supply too much data to that address. This overwrites its internal structures and can be used by malware to force the system to execute its code (Default = Enabled).

•

Computer Monitor: Comodo Endpoint Security raises an alert every time a process tries to directly access the computer monitor. Although legitimate applications sometimes require this access, spyware can also use such access to take screen shots of the current desktop, record browsing activities of the user and more (Default

= Enabled).




•

Disks: Monitors the local disk drives at the managed computer, for direct access by running processes. This helps guard against malicious software that need this access to, for example, obtain data stored on the drives, destroy files on a hard disk, format the drive or corrupt the file system by writing junk data (Default = Enabled).

•

Keyboard: Monitors the keyboard for access attempts. Malicious software, known as

'key loggers', can record every stroke made on keyboard and can be used to steal passwords, credit card numbers and other personal data typed through the keyboard.

With this setting is enabled, Comodo Endpoint Security generates alerts every time an application attempts to establish direct access to the keyboard


Note: The settings you choose here are universally applied. If you disable monitoring of an activity, entity or object using this interface it completely switches off monitoring of that activity on a global basis - effectively creating a universal 'Allow' rule for that activity . This 'Allow' setting over-rules any Ruleset specific 'Block' or 'Ask' setting for that activity that you may have selected using the 'Access Rights' and 'Protection Settings' interface.

Do NOT show popup alerts Configure whether or not the HIPS alerts are to be displayed at the managed computer for the end-user to respond. Choosing 'Do NOT show popup alerts' will minimize disturbances but at some loss of user awareness ( Default = Enabled).

If you choose not to show alerts then you have a choice of default responses that CES should automatically take - either 'Block Requests' or 'Allow Requests'.

Set popup alerts to verbose mode

Enabling this option instructs CES to display HIPS alerts in verbose mode, providing more more informative alerts and more options for the user to allow or block the requests (Default =

Enabled).

Create rules for safe applications

Automatically creates rules for safe applications in HIPS Ruleset (Default = Enabled)

Note: HIPS trusts the applications if:

•

The application/file is rated as 'Trusted' in the File List

•

The application is from a vendor included in the Trusted Software Vendors list

•

The application is included in the extensive and constantly updated Comodo safelist.

Set new on-screen alert timeout to

Determines how long the HIPS shows an alert for without any user intervention. By default, the timeout is set at 60 seconds. You may adjust this setting to your own preference.

Advanced Settings

Enable adaptive mode under low system resources

Very rarely (and only in a heavily loaded system), low memory conditions might cause certain

CES functions to fail. With this option enabled, CES will attempt to locate and utilize memory using adaptive techniques so that it can complete its pending tasks. However, the cost of enabling this option may be reduced performance in even lightly loaded systems (Default =

Enabled).

Block unknown requests when the application is not running

Selecting this option blocks all unknown execution requests if Comodo Endpoint Security is not running/has been shut down. This is option is very strict indeed and in most cases should only be enabled on seriously infested or compromised machines while the user is working to resolve these issues. If you know the managed computer machine is already 'clean' and are looking just to enable the highest CES security settings then it is OK to leave this option disabled. (Default =

Disabled)

Enable enhanced protection mode (Requires a system restart)

On 64 bit systems, enabling this mode will activate additional host intrusion prevention techniques to counteract extremely sophisticated malware that tries to bypass regular HIPS protection. Because of limitations in Windows 7/8 x64 systems, some HIPS functions in previous



HIPS Settings - Table of Parameters versions of CES could theoretically be bypassed by malware. Enhanced Protection Mode implements several patent-pending ways to improve HIPS. CIS requires a system restart for enabling enhanced protection mode. (

Default = Disabled)

Do heuristic command-line analysis for certain applications

Selecting this option instructs Comodo Endpoint Security to perform heuristic analysis of programs that are capable of executing code such as visual basic scripts and java applications.

Example programs that are affected by enabling this option are wscript.exe, cmd.exe, java.exe and javaw.exe. For example, the program wscipt.exe can be made to execute visual basic scripts (.vbs file extension) via a command similar to 'wscript.exe c:\tests\test.vbs'. If this option is selected, CES detects c:\tests\test.vbs from the command-line and applies all security checks based on this file. If test.vbs attempts to connect to the Internet, for example, the alert will state

'test.vbs' is attempting to connect to the Internet (

Default = Enabled).

•

If this option is disabled, the alert would only state 'wscript.exe' is trying to connect to the Internet'.

Background note: 'Heuristics' describes the method of analyzing a file to ascertain whether it contains codes typical of a virus. Heuristics is about detecting virus-like behavior or attributes rather than looking for a precise virus signature that matches a signature on the virus blacklist.

This helps to identify previously unknown (new) viruses.

Detect shellcode injections Enabling this setting turns-on the Buffer over flow protection.

Background : A buffer overflow is an anomalous condition where a process/executable attempts to store data beyond the boundaries of a fixed-length buffer. The result is that the extra data overwrites adjacent memory locations. The overwritten data may include other buffers, variables and program flow data and may cause a process to crash or produce incorrect results. They can be triggered by inputs specifically designed to execute malicious code or to make the program operate in an unintended way. As such, buffer overflows cause many software vulnerabilities and form the basis of many exploits.

Turning-on buffer overflow protection instructs the Comodo Endpoint Security to raise pop-up alerts in every event of a possible buffer overflow attack. The end-user can allow or deny the requested activity raised by the process under execution depending on the reliability of the software and its vendor.

Comodo recommends this setting is left enabled


You can also add files/folders and/or file groups to be excluded from Shellcode injections. To add exclusions, click the 'Exclusions' link after enabling this option.

The process of adding exclusions is similar to adding exclusions for virtualization in Sandbox

Settings. Refer to the explanation of adding files / folders to be excluded in the previous section




Sandbox Settings .

HIPS Rules

The 'HIPS Rules' screen allows you to view the list of active HIPS rulesets applied to different groups of or individual applications and to create and manage rules for the profile. You can change the ruleset applied to a selected application or application group.

Note : HIPS Rulesets are to be created before applying them to an individual application or an application group. Refer to the

next section Rulesets for details on creating new rulesets.

Application

Treat As

Actions

Column Header

HIPS Rules - Column Descriptions

Description

Name of the individual application or the application to which the ruleset is applied

The ruleset applied. For more details on the rulesets, refer to the next section Rulesets .

Contains control buttons to edit or remove the rule

Creating and Modifying Hips Rules

To begin defining an application's HIPS rule, you need take two basic steps.

•

Step 1 - Select the application that you wish the ruleset is to be applied

.

•

Step2 - Configure the rules for this application's ruleset

.

Step 1 - Select the application that you wish the ruleset is to be applied

•

To define a ruleset for a new application ( i.e. one that is not already listed), click the 'Add Rule' button at the top of the list in the 'HIPS Rules' interface.

The 'HIPS Rule' interface will open as shown below:



Because this is a new application, the 'Name' field is blank. (If you are modifying an existing rule, then this interface shows the individual rules for that application's ruleset).

•

To create a rule for a single application enter the file name of it in the 'Name' field

•

To create a rule for an application group, select 'Use Group' and choose the file group from the drop-down



Note : CDM ships with a set of predefined file groups containing collections of files under respective categories. Administrators can also create custom file groups with required applications. All the pre-defined and the custom file groups will be available in the drop-down. The custom file groups can be created under Settings > Global variables interface. Refer to the section

File

Groups for more details.

Step 2 - Configure the rules for this application's ruleset

There are two broad options available for creating a ruleset that applies to an application - Use a Predefined Ruleset

or Use a

Custom Ruleset .

•

Use a Predefined Ruleset - Allows you to quickly deploy an existing HIPS ruleset on to the target application.

Choose the ruleset you wish to use from the drop-down menu. The name of the predefined ruleset you choose is displayed in the 'Treat As ' column for that application in the 'HIPS Rules' interface.



Note : Predefined Rulesets, once chosen, cannot be modified directly from this interface - they can only be modified and

defined using the Ruleset interface. If you require the ability to modify components of the rule set, then you are effectively

creating a new, custom ruleset and should choose the more flexible Use Custom Ruleset option instead.

•

Use a Custom Ruleset - Designed for more experienced administrators, the 'Custom Ruleset' option grants full control over the configuration of each rule within that ruleset. The custom ruleset has two main configuration areas - Access

Rights and Protection Settings (Default = Enabled).



In simplistic terms 'Access Rights' determine what the application can do to other processes and objects whereas 'Protection

Settings' determine what the application can have done to it by other processes.

i. Access Rights - The 'Process Access Rights' area allows you to determine what activities can be performed by the applications in your custom ruleset.



Refer to the section HIPS Settings > Activities to Monitor to view a list of definitions of the Action Names listed above

and the implications of choosing the action from 'Ask', 'Allow' or 'Block' for each setting as shown below:

•

Exceptions to your choice of 'Ask', 'Allow' or 'Block' can be specified for the ruleset by clicking the 'Modify' link on the right.

•

Select the 'Allowed Files/Folders' or 'Blocked Files/Folders' tab depending on the type of exception you wish to create.

•

Clicking the 'Add' button at the top allows you to choose which applications or file groups you wish this

exception to apply to. ( click here for an explanation of available options).

ii. Protection Settings - Protection Settings determine how protected the application or file group in your ruleset is against activities by other processes. These protections are called 'Protection Types'.



•

Select 'Active' to enable monitoring and protect the application or file group against the process listed in the 'Protection

State' column. Select 'Inactive' to disable such protection.

Click here to view a list of definitions of the 'Protection Types' listed above and the implications of activating each setting.

Exceptions to your choice of 'Active' or 'Inactive' can be specified in the application's Ruleset by clicking the ' Modify' link on the right.

7. Click 'OK' to confirm your settings.

Rulesets

A Pre-defined ruleset is a set of access rights and protection settings that has been saved and can be re-used and deployed on

multiple applications or groups. Each ruleset is comprised of a number of rules and each of these rules is defined by a set of conditions/settings/parameters. Rulesets concern an application's access rights to memory, other programs, the registry etc.

The Rulesets screen under the the 'HIPS' tab displays the list of rulesets and allows you to add and manage new rulesets.

To add a new ruleset



•

Click the 'Add Ruleset' button

The 'HIPS Ruleset' dialog will appear.

above the list of rulesets.

•

Enter a name for the ruleset

•

Configure the Actions, states and exclusions for 'Access Rights' and 'Protection Settings' as explained above. Any

changes you make here are automatically rolled out to all applications that are covered by the ruleset. The new ruleset will be available for deployment to HIPS rule for applications/application groups from the HIPS Rules interface.

•

To edit a ruleset, click the Edit button under the Actions in the Rulesets interface. The Editing process is similar to the

Ruleset creation process explained above.

Protected Objects



The 'Protected Objects' panel under 'HIPS' tab allows you to protect specific files and folders, system critical registry keys and

COM interfaces at the managed computers, against access or modification by unauthorized processes and services. You can also add files in 'Protected Data Folders', so that 'Sandboxed' programs will be blocked from accessing them.

The 'Show' drop-down allows you to choose the category of protected objects to be displayed in the list and add and manage the protected objects of that category. You can add following categories of protected objects:

•

Protected Files - Allows you to view and specify programs, applications, files an file groups that are to be protected

from changes

•

Registry Keys - Allows you to view and specify registry keys that are to be protected from changes

•

COM Interfaces - Allows you to view and specify COM interfaces that are to be protected from changes

•

Protected Data Folders - Allows you to view and specify folders containing data files that are to be protected from

changes by Sandboxed programs

Protected Files

The 'Protected Files' list under 'Protected Objects' interface allows you to view and manage list of files and file groups that are to be protected from access by other programs, especially malicious programs such as virus, Trojans and spyware at the managed computer. It is also useful for safeguarding very valuable files (spreadsheets, databases, documents) by denying anyone and any program the ability to modify the file - avoiding the possibility of accidental or deliberate sabotage. If a file is 'Protected' it can still be accessed and read by users, but not altered. A good example of a file that ought to be protected is your 'hosts' file

(c:\windows\system32\drivers\etc\hosts). Placing this in the 'Protected Files and Folders' area would allow web browsers to access and read from the file as per normal. However, should any process attempt to modify it then Comodo Endpoint Security blocks this attempt and produces a 'Protected File Access' pop-up alert.

If you add a file to 'Protected Files', but want to allow trusted application to access it, then rules can be defined in HIPS Rulesets.

Refer to the explanation of adding 'Exceptions' at the end of this section for more details about how to allow access to files

placed in Protected Files.

•

To view the list of Protected Files, choose 'Protected Files' from the 'Show' drop-down in the 'Protected Objects'


Comodo Device Manager - Administrator Guide interface

The Protected File list is displayed under two categories, which can be selected from the drop-down at the right.

•

To view the list of individual files, programs, applications added to the

Protected Files list and manage them, choose 'File List'

•

To view the File Groups added to the Protected File list, choose 'Group

List'

You can add individual files, programs, applications or file/groups to 'Protected Files'.

To add an individual file, program or an application

•

Choose 'File List' from the drop-down at the right and click the 'Add File Path' button.



•

Enter the installation/storage path with file name of the file to be protected, in the managed computers, in the 'Add

Protected File Path' dialog and click 'OK'.

•

Repeat the process to add more files.

•

To edit the path of an item in the list, click the Edit icon under the 'Actions' in the list.

•

To remove an item from the list, click the thrash can icon under 'Actions' in the list

To add an application/file group to the Protected Files list

•

Choose 'Group List' from the drop-down at the right and click the 'Add Protected Group' button



•

Choose the file group from the drop-down and click 'OK'.

Note : CDM ships with a set of predefined file groups containing collections of files under respective categories. Administrators can also create custom file groups with required applications. All the pre-defined and the custom file groups will be available in the drop-down. The custom file groups can be created under 'Settings' > 'Global variables' interface. Refer to the section

File

Groups for more details.

•

Repeat the process to add more file groups.

•

To edit the path of an item in the list, click the Edit icon under the 'Actions' in the list.

•


Exceptions

You can choose to selectively allow another application (or file group) to modify a protected file by affording the appropriate

'Access Right' in ' HIPS Rules ' interface. A simplistic example would be the imaginary file 'Accounts.ods'. You would want the

'Open Office Calc' program to be able to modify this file as you are working on it, but you would not want it to be accessed by a

potential malicious program. You would first add the spreadsheet to the 'Protected Files' area. Once added to 'Protected Files',

you would go into ' HIPS Rules ' and create an exception for 'scalc' so that it alone could modify 'Accounts.ods'.

•

First add Accounts.ods to 'Protected Files' area as explained above .

•

Then go to 'HIPS Rules' interface and add it to the list of applications.

•

In the 'HIPS Rule' interface, enter the file name as account.ods, choose 'Use a Custom Ruleset' and select a ruleset from the 'Copy From' drop-down.

•

Under 'Access Rights' tab, set all the rules to 'Ask'



•

Click the 'Modify' beside 'Protected File/Folders'

•

Under the 'Access Rights' section, click the link 'Modify' beside the entry 'Protected Files/Folders'.

The 'Protected Files/Folders' interface will appear.

•

Under the 'Allowed Files/Folders' section, click 'Add' > 'Files' and add scalc.exe as exceptions to the 'Ask' or



'Block' rule in the 'Access Rights'.

Another example of where protected files should be given selective access is the Windows system directory at

'c:\windows\system32'. Files in this folder should be off-limits to modification by anything except certain, Trusted, applications like Windows Updater Applications. In this case, you would add the directory c:\windows\system32\* to the 'Protected Files area

(* = all files in this directory). Next go to ' HIPS Rules ', locate the file group 'Windows Updater Applications' in the list and follow

the same process outlined above to create an exception for that group of executables.

Registry Keys

The 'Registry Keys' list under 'Protected Objects' interface allows you to view and manage list of critical registry keys and registry groups to be protected against modification. Irreversible damage can be caused to the managed endpoint if important registry keys are corrupted or modified in any way. It is essential that the registry keys are protected against any type of attack.

To view the list of Protected Registry Keys, choose 'Registry Keys' from the 'Show' drop-down in the 'Protected Objects' interface

The Protected Registry Keys list is displayed under two categories, which can be selected from the drop-down at the right.



•

To view the list of individual keys and values, and manage them, choose 'Key List'

•

To view the Registry Groups, choose 'Group List'

You can add individual registry keys and Registry groups to Protected Registry Keys list.

To add an individual key

•

Choose 'Key List' from the drop-down at the right and click the 'Add Registry Key' button.

•

Enter the key name to be protected in the 'Add Registry Key' dialog and click 'OK'.

•

Repeat the process to add more keys.

•

To edit an item in the list, click the 'Edit' icon under the 'Actions' in the list.

•


To add an Registry group to the Protected Registry Keys list

•

Choose 'Group List' from the drop-down at the right and click the 'Add Protected Files' button



•

Choose the Registry group from the drop-down and click 'OK'.

Note : CDM ships with a set of predefined Registry groups containing collections of registry keys under respective categories.

Administrators can also create custom Registry groups with required key values. All the pre-defined and the custom Registry groups will be available in the drop-down. The custom Registry groups can be created under 'Settings' > 'Global variables'

interface. Refer to the section Registry Groups for more details.

•

Repeat the process to add more Registry groups.

•

To edit the an item in the list, click the Edit icon under the 'Actions' in the list.

•


COM Interfaces

Component Object Model (COM) is Microsoft's object-oriented programming model that defines how objects interact within a single application or between applications - specifying how components work together and inter-operate. COM is used as the basis for Active X and OLE - two favorite targets of hackers and malicious programs to launch attacks on a computer. It is a critical part of any security system to restrict processes from accessing the Component Object Model - in other words, to protect the COM interfaces.

The 'COM Interfaces' list under 'Protected Objects' interface allows you to view and manage list of individual COM classes and

COM groups that are to be protected by the Comodo Endpoint Security at the managed computer against modification, corruption and manipulation by malicious processes.

•

To view the list of Protected COM interfaces, choose 'COM Interfaces' from the 'Show' drop-down in the 'Protected

Objects' interface



The Protected COM Interfaces list is displayed under two categories, which can be selected from the drop-down at the right.

•

To view the list of individual COM Interfaces/Classes and manage them, choose 'Classes List'

•

To view the COM Groups and manage them, choose 'Group List'

You can add individual COM Interfaces/Classes and/or pre-defined COM groups to 'Protected COM Objects' list.

To add an individual COM object

•

Choose 'Classes List' from the drop-down at the right and click the 'Add COM Class' button



•

Enter the name of the COM object to be protected at the managed computer, in the 'Add COM Class Name' dialog and click 'OK'.

•

Repeat the process to add more COM objects.

•

To edit an item in the list, click the Edit icon under the 'Actions' in the list.

•


To add a predefine COM Group to the Protected COM objects list

•

Choose 'Group List' from the drop-down at the right and click the 'Add COM Group' button

•

Choose the file group from the drop-down and click 'OK'.



Note : CDM ships with a set of predefined COM groups containing collections of COM interfaces under respective categories.

Administrators can also create custom COM groups with required COM objects. All the pre-defined and the custom file groups will be available in the drop-down. The custom COM groups can be created under 'Settings' > 'Global variables' interface.

Refer to the section COM Groups for more details.

•

Repeat the process to add more COM groups.

•

To edit the an item in the list, click the Edit icon under the 'Actions' in the list.

•


Protected Data Folders

The data files in the folders listed under the 'Protected Data Folders' area cannot be seen, accessed or modified by any known or unknown application that is running inside the sandbox.

Tip

: Files and folders that are added to ' Protected Files ' interface are allowed read access by other programs but cannot be

modified, whereas the files/folders in 'Protected Data folders' are totally hidden to sandboxed programs. If you want a file to be read by other programs but protected from modifications, then add it to 'Protected Files' list. If you want to totally conceal a data file from all the sandboxed programs but allow read/write access by other known/trusted programs, then add it to

Protected Data Folders.

The Protected Data Folders list under Protected Objects allows you define protected data folders at the managed computers and to manage them.

•

To open the Protected Data Folders list, choose 'Protected Data Folders' from the Show drop-down in the Protected

Objects interface.

You can add standard folders at the managed computers as Protected Data Folders. Data files to be protected from sandboxed programs, can be saved inside the folders at the managed computers.

To add the path of protected data folder

•

Click the 'Add Folder' button at the top of the list


Comodo DM Admin Guide

HIPS Settings

HIPS Rules

Rulesets

Protected Objects

Related manuals

Table of contents

Comodo DM Admin Guide

HIPS Settings

HIPS Rules

Rulesets

Protected Objects

Related manuals

Novell

ZENworks Mobile Workspace 3.17.1

HP

Compaq t5730w Thin Client

HID Global

JQ66070BA

HP

Engage Go Mobile System

Meraki

Android Enterprise

Table of contents