Automation User Guide
Automation User Guide
Content
Upgrade
Device configuration
BlueCoat Proxy
IBM Qradar
Prerequisites
How to
Carbon Black
Fortinet FortiSIEM
Fortinet FortiManager
1
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
McAfee ESM
LogRhythm SIEM
Appendix
2
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Preface
IntSights delivers early warnings of hacking efforts and fraudulent attacks targeting a
specific user or individual company, via a sophisticated cyber intelligence platform.
IntSights delivers tailored intelligence by scanning a wide range of sources (e.g., the
Clear Web, Dark Web, Cyber-Crime Forums, IRC Channels, Social Media, App stores,
Paste Sites) and provides near-real-time alerts regarding cyber-threats.
IntSights’ virtual appliance connects the IOCs Management module running in the cloud
to your security/monitoring devices protecting your organizational network. The IOCs
Management module in the cloud aggregates numerous IOCs every day, acquired from
IntSights alerts, Intsights analysts research, 3rd party intelligence feeds, customer's own
documents and emails, and more. Every indicator is examined in order to validate its
severity and context, so the outcome is a tailor-made list of indicators to share with
security devices.
How it works
1. The IOCs Management in the cloud first collects cyber threat intelligence such
as malicious IPs, domains, file hashes, and URLs. It then validates if the
indicators are indeed a threat and that no legitimate assets are included (e.g.,
Google, home page for your organization, mail service, etc.)
2. The virtual appliance then pulls aggregated, enriched indicators from the
IOCs Management module in the cloud.
3. The virtual appliance shares the indicators with the security devices based on
the policy.
Attacks are stopped by security devices that are now updated with the latest
IOCs information.
3
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Unlike using an Ubuntu ‘open server’, in this case IntSights is responsible for the server
hardening, since its needs to meet the application requirements.
Guidelines
● General structure of the appliance is container based, which means that
each execution unit resides within its own siloed environment, which
reduced the attack & exploitation surface significantly.
● Ubuntu Hardening:
○ Standard shell is disabled for all users, and the only available shell
is the intsights appliance custom CLI, which has an expert mode
shell that can be removed if required.
○ The only services that are open and available are services that are
required for the platform’s operation. No other services are
installed that are not required.
4
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
5
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Prerequisites
● Virtual infrastructure (e.g. VMware vSphere)
● Network connectivity between the appliance to / from the security devices for
IOC
sharing (Ref table below)
The Virtual appliance requires access to all subdomains of every URL under these domains.
6
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Network connectivity
HTTPS (443) Incoming (to the From the internal network to the virtual appliance
appliance) “Management” interface. For administration
SSH Incoming (to the From the internal network to the virtual appliance for
appliance) administration
8080 + 9090 Incoming (to the From the various security devices to the virtual appliance for
appliance) pulling IOCs
443 Outgoing (from the From the virtual appliance to IntSights Cloud (Internet).
appliance) During first initial installation and upgrade access is required
to:
*.intsights.com, *.gcr.io, *.googleapis.com, *.docker.io,
*.cloudfront.net
Per device connectivity Outgoing or Incoming From the virtual appliance to the various security devices, for
(Ref: “Integration” section) pushing IOCs
7
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
3. Click “Download”
If you are using Microsoft Azure / Amazon AWS infrastructure, please contact IntSights to
schedule an installation.
8
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
9
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
b. Apply changes.
It is highly recommended to use a static IP since this IP will be configured as a feed source in
the security devices. Retain the IP address, as you will need it to log in to the web console
10
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Obtain the API key from the Integration page in the cloud platform
b. Click Next.
11
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
d. Create an Admin user. This user is different from the Admin user
created previously and is used only for web access to the virtual
appliance.
e. Click Next.
g. When finished, you should see the main virtual appliance configuration
page
12
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Upgrade
There are two options to perform an upgrade
3. If there is an upgrade available, you will see a notification in the top of the
page
4. Click ‘Upgrade'
13
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Make sure you are using latest software release before proceeding with adding devices.
14
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Device Integration
15
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
2. Create at least one policy rule to share threat indicators with the device.
Note: You can also create an IOC group and link it to the device without a
policy rule, this will be explained later.
3. Complete the required configuration in the device to use the IOC retrieved
from the virtual appliance.
Integration types
There are two types of integration methods - “Push” and “Pull”:
Pull
The device pulls IOCs from the virtual appliance in a predefined schedule.
Push
The virtual appliance connects to the device and pushes new IOCs periodically.
16
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Forcepoint Triton Ap-Web 8.3 or higher Push - TCP 15873 API account
Palo Alto Firewall 6.0.x-7.0.x Domains, URLs - Push User with Read/Write access to the Rest API
http/https
IPs - Pull
Check Point Firewall R77.30 Push - SSH (22) Admin user with BASH as default shell (IOCs are
pushed through SSH)
Splunk Standalone 6.5.3 Push - 8090 User with Read/Write access to the Rest API
Zscaler Web Push – HTTPS (443) Console user and API key
Microsoft O365 – Exchange Latest (Cloud) Push – HTTPS (443) Office 365 admin username and password
Online
17
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
c. Active Directory
For ‘Pull’ devices you only need to provide the IP address or hostname of the device.
18
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
d. IP Address or Hostname
6. Click Create
8. Also verify that the device appears in the integration page in the cloud
platform
19
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Policy
Group of rules for the same threat type (eg Phishing, Data Leakage, IOC Management
etc)
There are 2 types of policies:
Rule
Set of conditions and actions that define the automation behavior. Each rule is
combined of:
● Threat profile – Defines the alerts or general risk that will be handled by the
rule
IOC group
A container of threat indicators (IOC). Each rule in the policy must be linked to an IOC
groups and the IOC group must be linked to a device. The list of IOCs in the IOC group
will be shared (Pull / Push) with the device
20
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
4. Select the policy you want to use based on the threat you want to mitigate.
21
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
22
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
If a condition does not have any value selected, it means that it will not be considered
as a criteria for matching alerts
5. Click Next
23
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
4. You should see the newly created IOC group linked to the device
24
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
IOC group created will be available for the same device in all other policies
7. Click ‘Save’
25
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Historical alert selection is available only at the first initial time you create the rule,
and can not be modified once enabled
26
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
a. Severity
b. Type
27
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
8. Click finish
28
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Overview
Active Directory integration allows the IntSights platform to provide indication and
mitigation for leaked user account credentials. In case the system locates a user
account that was leaked, it validates it with Active Directory if the account is valid and
sets the severity level in accordance.
When a leaked account is found, the account name is searched across one or more
domains, so even if the external domain (the one that was configured as an asset and
that triggered the alert) is different than the internal domain, the system will still find
the account.
1. Example:
2. The system checks if users ‘bob’ and ‘john’ appear in the following domains
Internal.company.com
company.com
On top of active account validation, the system can validate if the matching clear text
password is valid or not.
29
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Prerequisites:
● Network connectivity over LDAP or LDAPS from the virtual appliance to the
required domain controller/s.
● List of one or more domains that hold the user directory.
The list of domains will be used as a baseline for searching active users.
● List of corresponding Domain Controller/s IP address per domain.
● A domain user and password
● For account and password validation
Use a dedicated service account, with the minimal permissions necessary. There
is no need for administrative privilege or specific group membership.
● For remediation
Use a dedicated service account, with permissions to perform the required
remediation actions.
30
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
○ Domain name
○ Click Add.
31
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
If needed enable password policy validation and login attempt rate limit
32
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Remediation option can be enabled only if ‘Leaked user account and password
validation’ is enabled
33
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
34
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Background
IntSights platform shares threat indicators with Palo Alto Panorama or Firewall by
adding IOCs to a Dynamic object group. The Dynamic group is then used in the Palo Alto
Firewall policy in the Sources or Destination sections of the rule.
Palo Alto Dynamic object groups can include on type of IOC. This means that you need to have
separate groups for IP, Domains or URL IOCs.
35
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Note: Make sure to copy the IOC group URL from the device instance in the
integration page
2. Click New.
Make sure to choose the same IOC type you configured in (IP List in this example).
36
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Versions 6.x-7.0.x
In PANOS versions 6.x-7.0.x, the process of populating an IP list is different from the
process of populating domains and URLs.
Use the same Pull method as described for PANOS 7.1, with the exception that one
must use a Dynamic Block List object instead of a Dynamic External List, as in PANOS
7.1.
Make sure to copy the IOC group URL from the module -> Integration page.
virtual pushes URLs and Domain lists to a custom object of type URL Category
Here is an example of a URL Category. The List name is Domain, and the device is
PAN_6:
37
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
38
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Perquisites
Management server version R77.30 with R77.30 Add-On (Check Point solution ID:
sk105412)
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails
=&solutionid=sk105412
Make sure you install the required add-on to the gateway before you proceed.
How it works
In this Integration, the virtual appliance is updating the indicators file on the
Management server (e.g., ’SmartCenter’) which is then updating the threat prevention
blade of each of the relevant Firewall gateways.
1. Every time the IOC bundle changes (new IOCs added) open an SSH connection to
the Management server, and login using an admin account with expert/bash
access.
2. The virtual appliance copies a file containing the latest IOCs bundle in CSV format
to the Management server.
39
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
3. Note that while creating the bundle for a Check Point device you define
the action type: M
onitor / Block
i. Login to SmartDashboard.
40
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
iii. Under Indicators you should see all the IOC lists that have been
pushed to the Firewall:
41
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
BlueCoat Proxy
In this integration, the BlueCoat proxy gateway pulls the IOCs from the appliance. Make
sure to copy the URL from the Automation -> Integration page.
42
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
3. Click New.
43
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
6. Deploy changes.
44
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
45
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
In this integration, the virtual appliance can send:
● Threat Indicators
● Tailored intelligence alerts
Pushing alerts applies to both standalone version and Enterprise Security version,
though it’s only used through the standalone data inputs.
Threat Indicators
Prerequisites
Once you have added Splunk to the appliance integrations, you will see the IOC app in
the list of apps.
46
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Background
Pushing alerts to Splunk is done vis the HEC (HTTP Event Collector). Before you add the
Splunk to the Virtual appliance or if you are using an existing integration make sure to
generate a HEC token as described below
Prerequisites
Integrate Splunk to the virtual appliance (or add the HEC Token to an existing
integration)
47
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
1. On splunk page, click the Settings menu, and then choose Add Data.
2. Choose monitor category, and on the left menu choose HTTP Event Collector.
3. Fill in the desired name of the HEC token (e.g intsights_alerts)
4. Click Next.
5. On S ource Type, choose S
elect , filter and choose _ json.
6. Press Review, and Submit
7. Copy the toke value and use it in the Virtual appliance to add a Splunk
integration or edit an existing one
48
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
IBM Qradar
49
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
7. Add Qradar as a Push device to the virtual appliance using the credentials and
token you just created.
9. Under “Reference Set Management” you will see the IOC lists that were added.
50
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Prerequisites
1. Triton Management server
3. API account
The policy server API module is not installed by default and can be installed only on
Linux. Ref: Linux management API install
http://www.websense.com/content/support/library/web/v83/mgmt_api_install/install_
guide.pdf
How to
1. Add the policy server as a Push device to a virtual appliance.
51
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Carbon Black
In order to successfully integrate with the device make sure to complete:
● Step 1 - Add device to the appliance
For device using ‘Pull’ mode don't forget to copy the IOC group URL
● Step 2 - Creating automation rules
How to
1. Log in to the Carbon Black Management console.
52
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Fortinet FortiSIEM
In order to successfully integrate with the device make sure to complete:
● Step 1 - Add device to the appliance
For device using ‘Pull’ mode don't forget to copy the IOC group URL
● Step 2 - Creating automation rules
2. Navigate to CMDB.
53
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
6. ClickOK.
v. Data Mapping -
54
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
4. Click Save.
11. Click the green + and choose the desired update schedule.
55
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
4. Click OK.
56
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
7. Check the Up
date via
API button, and click Add.
57
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
d. Data Mapping
e. Click Save.
10. Click the green + and choose the desired update schedule.
a. Click Close.
58
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
4. Click OK.
59
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
9. Click Save.
10. Click the green + and choose the desired update schedule.
60
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
61
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Fortinet FortiManager
In order to successfully integrate with the device make sure to complete:
● Step 1 - Add device to the appliance
For device using ‘Pull’ mode don't forget to copy the IOC group URL
● Step 2 - Creating automation rules
How to
1. Log in in to Fortimanager Management console.
2. Navigate to Policies & Objects -> Objects Configuration -> Security Profile
-> Web filter
62
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Background
In this integration the virtual appliance sends IOC with context to the ArcSight SIEM. IOC
with context includes, on top of the IOC value (IP address, Domain, URL or Hash)
contextual information about the threat related to the IOC.
Contextual data is sent by default for all IOCs, there is no need to enable it specifically
Requirements
1. ArcSight Management (ESM)
2. FlexConnector installed
3. ArcSight Console
63
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
C:\ProgramFiles\ArcSightSmartConnectors\current\user\agent\flexagent\intsights
version.order=1
version.id=10.1
version.query=SHOW server_version
query=SELECT ioc_id, ioc_type, ioc_value, ioc_action, batch_id FROM iocs WHERE
batch_id > ? ORDER BY batch_id ASC
# more properties
maxid.query=SELECT max(batch_id) FROM iocs
id.field=batch_id
uniqueid.fields=ioc_id
# event mapping
event.deviceCustomString1=ioc_value
event.deviceCustomString1Label=__stringConstant("IOC value")
event.deviceCustomString2=ioc_type
event.deviceCustomString2Label=__stringConstant("IOC type")
event.deviceCustomString3=ioc_action
event.deviceCustomString3Label=__stringConstant("IOC list action")
event.deviceVendor=__stringConstant("Intsights")
event.deviceProduct=__stringConstant("Intsights Virtual Appliance")
64
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
At this point, we describe our best-practice for creating and populating
ArcSight Active Lists that contain IOCs.
2. Select Lists.
65
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Create four Active Lists, one for each IOC type (IP, URL, Domain and Hash):
66
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Type should be: ‘String’, except for IP where the type should be ‘IP Address’
67
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Attributes
68
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Conditions:
69
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Aggregation:
70
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Actions
71
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Attributes:
72
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Conditions
73
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Aggregation:
74
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Actions:
Please note that only for IOC type IP the field value in the rule should be ‘StringToIP’
instead of ‘Custom String1’ that is used for Domain, URL and Hash IOCs
Once the Active Lists are in place, it is possible to create block/monitor rules, along with
more sophisticated deployments.
75
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
McAfee ESM
In order to successfully integrate with the device make sure to complete:
● Step 1 - Add device to the appliance
For device using ‘Pull’ mode don't forget to copy the IOC group URL
● Step 2 - Creating automation rules
1. Create a watchlist
2. Create an alarm
Create a watchlist:
1. Log in to McAfee ESM Management console.
2. Select Watchlists:
76
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
77
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
b. Add the URL taken from the device integration IOC list (ref page 14).
c. Authentication: None
d. Method: GET
e. Test connection
78
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
b. Finish
Create an alarm
1. Select Watchlists
79
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
3. Under Condition, add your Match condition. The example below uses
‘Field Match’ to match between Domains and File Hashes to IOCs from
IntSights.
80
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
81
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
LogRhythm SIEM
In order to successfully integrate with the device make sure to complete:
● Step 1 - Add device to the appliance
For device using ‘Pull’ mode don't forget to copy the IOC group URL
● Step 2 - Creating automation rules
● The integration supports multiple IOC groups, where each group support
multiple IOC types (eg. Domain, IP or URL).
● Each IOC group is translated by the system to a TAXII collection, and the IOCs are
converted to STIX documents that are pulled by the LogRhythm device.
Prior to performing the steps below first complete steps 1 and 2 in this guide (add the
LogRhythm to the virtual appliance and sync IOC groups).
82
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
3. CD to the directory C:\Windows\System32\drivers\etc" and type "notepad hosts"
4. Add an entry with the IP address of the appliance and point it to ‘agent-taxii’
1. User = logrhythm
2. Password = l ogrhythm
3. Endpoint
https://<appliance ip addr>:9000/services/collection-management-logrhythm
Make sure to input the IP address if the virtual appliance in the URL
83
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
1. If you see error like ‘Feeds not found for the provider’ it means
everything works properly, but no IOC groups are configured on
the IOC management module.
84
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
85
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Required information
86
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
3. Under user defined you will see the IOC groups and the IOCs
87
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Background
IntSights platform shares threat indicators with Exchange online and uses the
Domain IOCs – Are added to the protection spam filter blocked domain list
IP Address IOCs – Are added to the protection connection filter IP block list
88
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
8. Test connection.
9. Click Create.
89
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
4. In the Internal remediation section select an IOC group that is linked to the
Exchange online
90
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Example:
1. IP IOCs
Will appear under the default policy -> Block lists -> Domain Block list
2. Domain IOCs
Will appear under the SPAM policy -> Block lists -> Domain Block list
91
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
92
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
Appendix
How to install a new certificate
3. Type the following command to enter a shell inside the appliance external
connection service.
root@agent-synchronizer:~/agent/agent_services/synchronizer#
5. Input
cd /usr/share/ca-certificates
/usr/share/ca-certificates/custom/[Certificate].crt
93
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.
10. Run
pkg-reconfigure ca-certificates
94
Proprietary and confidential IntSights Cyber Intelligence Ltd. Copyright © All Rights Reserved 2018.