This articles explain how to configure Oracle App in order to retrieve logs from a specified database table.
Requirements:

• SGBox version 4.2.5

Go to the application lists from SGBox go to SCM > Applications

Select Vendors Integrations and download the application Log from Oracle. Click on INSTALL. Once Installed click on EDIT icon

You need to configure the application as follow:

Host: Database IP
SID: Oracle SID
Port: DB port
Username: Oracle user used to login
Password: Oracle user's password
Star Date: Initial date to retrieve logs
Timestamp field: The Column name that contain the timestamp
Timestamp table: The table that contain the timestamp
Separate field: Character used to separate information once retrieved
Query: query used to extract information

IT’S VERY IMPORTANT TO NOT PUT ANY TIMESTAMP CONDITION OR * IN THE SELECT FIELD

After configured you need to schedule the application to be executed. See this section to know how to schedule an application.

The first time the application has been run some components are added and if everything is ok you can see in LM > Analysis> Historical Search the results

Once executed you’ll see your logs LM > Analysis > Historical Search

If yuo have more databases or more SQL Server you can clone it and configure a new one.

This articles explain how to configure MySQL App in order to retrieve logs from a specifc database table.
Before start here you can see how our database is configured:

Requirements:

• SGBox version 4.2.5

Go to the application lists from SGBox go to SCM > Applications

Select Vendors Integrations and download the application Log from MySQL

You need to configure the application as follow:

Host: Database IP
Username: SQL user used to login
Password: SQL user's password
Star Date: Initial date to retrieve logs
Timestamp field: The Column name that contain the timestamp
Timestamp table: The table that contain the timestamp
Separate field: Charater used to separate information once retrieved
Query: query used to extract information
DB name: The database name

After configured you need to schedule the application to be executed. See this section to know how to schelude an application.

Once executed you’ll see your logs LM > Analysis > Historical Search

If yuo have more databases or more SQL Server you can clone it and configure a new one.

This articles explain how to configure MSSQL App in order to retrieve logs from a specificd database table.
Before start here you can find how our database is configured by logging in with SQL Authentication:

You can see:

• In red: the database configuration
• In black: the query results

Requirements:

• SGBox version 4.2.5
• The SQL Authentication must be used to execute the query

Go to the application lists from SGBox go to SCM > Applications

Select Vendors Integrations and download the application Log from SQL Server

You need to configure the application as follow:

Host: Database IP
Connection string: Used connect to the database
Username: SQL user used to login
Password: SQL user's password
Star Date: Initial date to retrieve logs
Timestamp field: The Column name that contain the timestamp
Timestamp table: The table that contain the timestamp
Separate field: Charater used to separate information once retrieved
Query: query used to extract information

After configured you need to schedule the application to be executed. See this section to know how to schelude an application.

The first time the application has been run some components are added and if everything is ok you can see in LM > Analysis> Historical Search the results

Once executed you’ll see your logs LM > Analysis > Historical Search

If yuo have more databases or more SQL Server you can clone it and configure a new one.

This article explains how to configure SGBox APP in order to restore your log or Database to SGBox.

Requirements:

• SGBox version 4.2.4
• Shared Forlder on your server.

Install SGBox Backup Application: SCM > Applications > Backup
You can choose to use SMB or NFS protocol to restore your files. After installed you need to configure it.

Click PLAY and wait 90 seconds to start restore process:
If you select Raw log data you need also to specify a start date and host list you want restore.

If you select SGBox Database you need also to specify a start date you want restore.

The behavior analysis is an extension of the Risk Analysis and takes into consideration all the events related to the user and performs a series of evaluations to define whether the behavior of a certain user is considered “normal” or not.
Statistical algorithms analyze the historical data related to the user, the actions performed and the hosts on which these actions took place.

Requirements:

• SGBox Version 4.2.1.
• The User Behavior Analytics must be unlocked. Contact us for more information.

Examples of anomalies:

• the user Mario always connects in VPN every morning at 9 AM. One day starts the VPN at 3AM.
• the user Giovanni has never accessed to the core switch. One day he access.
• the user Luigi has never seen before. One day he login to a Windows system.

Evaluations performed:

• is the user known?
• has the user already performed this particular action?
• has the user already performed this particular action in this time interval?
• has the user already performed this particular action on this host?
• how do other users behave about this particular action?

The purpose of this analysis, as said, is to define if a behavior can be considered ’normal’. All the different algorithms applied to the historical data, will define the score (risk level) that will be assigned to the user.

UBA Configurations

Only few parameters can be modified to fine tune the user behavior analysis algorithms. In the “advanced options” section, you can:

• enable or disable the learning mode. If unchecked the learning mode is disabled, and the analysis will be performed. If you enable this flag you should also define an expiration date of the learning mode, when the learning mode will be automatically disabled. If you enable this flag with few events it is possible that you start receiving a lot of warning messages, since there’s no history.
• define an email address that will receive all the messages coming from the behavior analysis
• by default everything that happens during the last (by default) 15 days represent the analysis base. Meaningful values varies from 15 to 30 days
• You can define a retention time for the users baseline. This is generally two times the analysis base and the acceptable range is between the analysis base value and 60.
• last option represents the minimum percentage beyond which the event is considered to be at risk.

You can also specify with events are involved in UBA by enable them in LM > User Behavior Analytics.
Here is also required to select the User Parameter.

Dashboards
Results should be accessed by dashboards. The application will deploy four new dashboards called “User Behavior Analytics – *”. Please take a look at the dashboards and don’t forget that while the application is in learning mode, nothing will be displayed.
The application also enables a new widget called “User Behavior analytics”. You can create your own dashboards by mixing different views enabled by this widget.

Lists
The application will modify also the Lists view (SCM > Actions > Lists) by adding a new column called “UBA”. When a list file is selected, this will be used in the user behavior analysis application to match the current user with other users. List file should contain a set of users that should belong to the same group (or role) of the current user. You can use a group to include and/or exclude a user from a group. If both include and exclude flag are selected, the list is used first as an include list and if there is no match, it will be used as an exclude list (compare user behavior against users not present in that list).