Let Oomnitza be your single source of truth!
You'll get visibility of your devices as data from Sophos Endpoint Security is automatically transformed into consumable information and actionable insights.
Connect Oomnitza and Sophos in minutes
Get the information and insights that you need to reduce costs and the time that you spend on administration tasks such as:
- Configurable dashboards and list views of key user information
- Configurable reports to share information about your users with your colleagues and management
Configurable workflows that you can create such as:
- Retrieving a users role
- Deactivating and deleting users
Before you start
Integrate Sophos Endpoint Security with Oomnitza
- In Oomnitza, click Configuration>Integrations>Overview.
- Click Block view .
- On the Integrations page, scroll down to the Extended section for user integrations.
- Click NEW INTEGRATION.
- Search for the integration in the sidebar.
- Click ADD.
Before you start
More information is provided about the following fields to help you complete the integration:
Integration preferences: By default, the option Create & Update is selected, which allows for editing existing user records and adding new ones. If your goal is only to edit existing user records, choose Update Only. On the other hand, if you only want to add new records, select Create Only.
User selection: Select User only to create user records and add them to the People object. Select User plus SaaS User to create and add user records to the Software > SaaS object. Once your users are created in the SaaS menu, you can create SaaS user workflows to validate the existence of a given user in a SaaS system and to pull role information from your SaaS System. For steps see Creating SaaS user workflows.
When you select User plus SaaS User and you have multiple instances of the same SaaS, you can choose your SaaS instance from the dropdown. If you have a single instance of the SaaS, your instance is already detected by the system.
To review or update the integrations details, click Edit :
- Update the integration name if necessary.
- From the User Selection list, select an option.
- For installation type decide whether you want to store the credentials locally or in Oomnitza:
- Select Local if you want to store credentials locally.This mode does not support OAuth or AWS.
- Select Cloud if you want to store credentials in your Oomnitza instance.
- For integration preferences, select an option.
- Enter the name of the integration user.
Choose one of the following options:
- Select the credentials that were created for the integration.
- Edit the credentials that were created for the integration.
- Create new credentials
By default, user data is streamed to Oomnitza once every day.
You can configure the schedule to meet your needs such as changing the interval or changing the time so that the data is streamed when your system isn't busy.
- Click Edit .
- Configure your schedule.
- Click Update.
To map the fields to Oomnitza, click Edit :.
Creating custom mappings
Map the Sophos fields to Oomnitza fields and create custom mappings to get the user information that you need.
Complete these actions:
- Click Smart Mapping to automatically detect appropriate mapping fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
- Create a custom mapping for the Sophos ID. To do this, complete the following steps:
- Select the down arrow on the ID field that you want to map.
- Select Add new Oomnitza users field.
- Change the name of the field to Sophos User Id.
- Select the Unique checkbox.
- Click CREATE.
- Ensure that the Email is mapped to the
- Username field on the Oomnitza side (required for integration).
- Email field on the Oomnitza side (required for integration).
- Select the Role field on the Oomnitza mapping side.
- Choose a suitable role from the list (a defined role is necessary for the integration)
- Assign a sync key to a unique field, such as the Email.
- Click UPDATE.
Tracking information for user loads
When the integration is run, you can track the name of the credentials that were used and the source of the data. To do this, you map the following fields to Oomnitza:
- Connect: Credentials
- Connect: Data Region
- Connect: Tenant ID
Standard Sophos to Oomnitza mappings
The following Sophos fields can be mapped to Oomnitza:
Connector Sync Time
Source of User (custom, activeDirectory, azureActiveDirectory)
Did you know?
You can define rules for your integration by selecting Edit integration on the mapping page. For example, you may only want to run the integration if a certain contact or region exists. See Filtering integration results.
You can add new fields to your integration by selecting Add new field on the mapping page. All you need to do is specify the property name. See Creating custom API fields.
Launching the integration
Your integration is in Draft mode until all the required mandatory fields are added. Once you have added all of the required fields, select Launch to activate your integration.
If you selected Cloud as the installation type when creating the integration, refer to Running an extended integration
If you selected Local as the installation type when creating the integration, refer to Running an extended integration locally.
Getting your results
To view the information that is collected about your assets, click Assets. To view the information about software, click the Software tab.
To view the information that is collected about your users, click People. If you selected User plus SaaS User when running the user integration, you can also find a list of users in the Software > SaaS menu
Create workflows using the SaaS User Role retrieval block
You can create a Saas User workflow in Oomnitza using the Sophos User Role preset. This preset sets the Role to User for all users retrieved.
Before you create a SaaS user workflow, you should have already run your extended user integration and selected User plus SaaS User to populate the software entry in the Software > SaaS menu.
To create a Saas User workflow using the Sophos User Role preset, complete the following steps:
- Click Configuration > Workflows > Saas Users from the menu.
- Click Add (+). The Begin and End blocks are automatically added to the sandbox.
- Enter the name and a description of the workflow.
- Edit the Begin block by adding the rules that will trigger the workflow. For further information see SaaS User Roles.
- Click the Blocks tab, and drag and drop the SaaS User Role retrieval block onto the canvas.
- Click the Edit icon.
- Enter Sophos in the search field and choose the Sophos SaaS User Role preset.
- Click the right arrow >.
- Enter your Credentials.
- Your Sophos information is derived from the global variables you created in Adding Sophos Endpoint Security global variables or can be entered manually.
- Select the Deactivate User checkbox to deactivate the SaaS user in SaaS > Sophos > Users if they are not found in your Sophos instance.
- Click SAVE.
- Connect the blocks.
- Save, validate, and activate your workflow.
To view active Sophos users in the SaaS Users UI, complete the following steps:
- Click Software from the menu.
- Select the Saas tab, and select your software entry for Sophos.
- Click Users in the side pane.
- The Role column is populated with the user details to confirm that this user has been found in your Sophos SaaS.
Create an offboarding workflow using an API block. Select the following presets:
- Sophos Delete User preset deletes a Sophos User.
When creating the offboarding workflow, ensure that the Begin block criteria accurately identifies inactive users. For example, for SaaS user workflows you can set the To be Deleted in SaaS flag to Yes, or for People workflows, you can set the Offboarding Date to Current date.
Reference articles for creating workflows
Unleash the power of Oomnitza
To get valuable actionable insights that help you manage your assets, learn how to:
- Configure dashboards for your assets and software
- Configure custom reports about your assets and software
See Getting started.