<< PREVIOUS  NEXT >>

 

 ADD APPLICATION SERVICE AND PROCESS

  1. Provide Service Name, Service Tag, Service Type and Operating System Platform

  2. The provided service tag can be utilized during  VSP probe installation to enable automatic provisioning into the Application Service

  3. Select the Deployment Type as VM

    Picture 1073742165

  4. Provide the below information about the process:

     

    Field Name Details/Examples

    Process Name

    Name of the Process

    Process Description

    (Optional) A short description of the process

    Select Process Type

    Select the appropriate process type from the drop-down. Eg: Java, Binary, .NET

    Protection Profile Name

    Select the appropriate Protection Profile from the drop-down. Refer to Section Create Protection Profile of  Operations for more information. A link to create a new Protection Profile is also provided

    Web Profile Name

    (For VSP-Web only) Drop-down list with all available Web Profiles. Refer to the section Web Profiles in the topic Operations for more information

    Select Vulnerabilities

    Based on the selected Process Type, select the vulnerabilities against which VSP Protection is desired. The protection level can be configured for each vulnerability. By default, when a vulnerability is selected, the associated protection mode is set to Detect
    Note: XML Injection protection includes DTD Injection, also called XML External Entity (XXE) Injection. XXE attacks manipulate the DTD, allowing an attacker to view files or access other network resources to which the server has access. To detect XXE injection, the following vulnerabilities must be enabled - Path Traversal Injection, Remote File Inclusion and Local File Injection

    Auto-Instrumentation (VMs only)

    Enable – When enabled, instrumentation is performed by VSP at the back end and no manual configurations are required
    Disable – When disabled, instrumentation must be performed manually. Refer to Section Application Instrumentation  for more information

    Note: Refrain from using auto-instrumentation with WebSphere. Opt for manual instrumentation. Refer to the WebSphere App Instrumentation section for more information

    Application Deployment Folder

    (For FSM only) Location where the application is deployed.

    Eg: /opt/tomcat/webapps

    File Integrity Exclusion Folders

    (For FSM only) List of directories to be excluded from FSM separated by comma. Eg: /opt/tomcat/logs,/opt/tomcat/work

    File Integrity Monitored Folders

    (For FSM only) List of additional directories to be included for FSM monitoring. Eg: /usr

    File Extension Exclusion List

    List of file extensions to be monitored by FSM. Eg: *.log

    Start Up Script File Path

    Full path (with the executable name) of the Web Server/Application Server start up script.

    Eg: /usr/local/apache2/bin/run_apache.sh

    Application Type

    (For VSP-Web only) Select the Application Type from the drop-down.

    Eg: Confluence, Normal, JIRA

    Server Type

    (For VSP-Web only) Select the Server Type from the drop-down.

    Eg: JBoss, Weblogic, Tomcat

    LFI Profile Name

    Drop-down list with all available LFI Profiles. Refer to Section LFI RFI of Operations for more information

    RFI Profile Name

    Drop-down list with all available RFI Profiles.Refer to Section LFI RFI  of  Operations for more information

    Table – Process Collective Details

  5. Click SAVE 

 

<< PREVIOUS  NEXT >>