<< PREVIOUS NEXT >>

 

 

APPLICATION DISCOVERY WORKFLOW

 

The high level Application Discovery workflow is depicted below: 

image150

Figure - Application Discovery Workflow

 

  1. After probe installation, Application Discovery collects information about running applications on the host

  2. Based on this information, a new application is created or the instance is associated with the existing application on CMS. A system alert is generated for auto-association of instances

    1. Navigate to Manage > Web > Application Provisioning in the left navigation pane to view the application 

      image151

    2. The name of the newly created Application is of the format: <Process Type>_<Deployment Folder>_<Application Server>_<Application Server Version>

    3. Example: JAVA17_opt_my_app_Tomcat_10.0

    4. For .NET and .NET Core Applications, the name of the newly created Application is of the format: <SiteName_or_SubSiteName_OnIIS>. The .NET version number is also populated on the UI 

       

      NOTE:

      The slashes ("/" OR "\") in the directory paths are replaced with underscore ("_") The maximum number of characters for the application name is 55. In cases where the number is exceeded, it is truncated

      image152

    5. The auto-discovered applications have the Created By field as System 

      image153

    6. During upgrade scenarios from VSP 2.5/2.6 to VSP 2.7, review both the discovered applications from VSP 2.7 and user-created applications from VSP 2.5/2.6 after Application Discovery scan. Delete the applications that are not needed

  3. Once the application is created, the user may configure the security policy by editing the newly created process:

    image154

    1. Create the required protection profile, web profile, LFI/RFI profiles. Associate them with the application

    2. Select vulnerabilities

      image155

    3. The auto-discovered fields – Process Type, Application Deployment Folder, Start Up Script File Path, Server Type - cannot be modified since they are auto-discovered. Other fields including the names of Application, Service and Processes can be modified

      image156

      NOTE:

      In cases where the security profile is not configured and the process is not running on the instance, another Application Discovery scan removes the newly created application

      For WebSphere, the auto instrumentation option is disabled by default

       

  4. Once the security profile is configured, the application is auto-provisioned and moves to 100% completion

    image157

  5. Restart the business application (application process) to enable security policies in the application. This restart is required only during the first-time selection of security policies. Subsequent changes to the security policies do not require an application restart

 

<< PREVIOUS NEXT >>