Send Cisco Umbrella and Secure Access logs to LogPulse
Cisco Umbrella and Cisco Secure Access logs from the S3 bucket they are written to: DNS, web proxy, cloud firewall, intrusion prevention and the admin audit log.
Configure → Sources → Cloud. LogPulse reads the S3 log bucket (Cisco-managed or your own) itself, without an agent. Events land in the dns, web, firewall, network, audit indexes with source cisco_umbrella and fill the Network Resolution (DNS), Web, Network Traffic, Intrusion Detection, Change data models.Overview
- S3 log bucket (Cisco-managed or your own) to Integration poller
- Integration poller to index=dns
- Integration poller to index=web
- Integration poller to index=firewall
- Integration poller to index=network
- Integration poller to index=audit
LogPulse signs in to Cisco Umbrella and Secure Access with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- Logging to S3 turned on in Log Management
- An access key that can list and read the bucket
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in Cisco Umbrella and Secure Access
| Field in LogPulse | Where you find it |
|---|---|
| S3 bucket | In Umbrella or Secure Access: Admin, Log Management. A Cisco-managed bucket or your own. |
| Region | The AWS region of the bucket, shown next to it in Log Management. |
| Data path (optional) | The folder before dnslogs/ and proxylogs/. Leave empty when the logs are at the root of your own bucket. |
| Access key ID | For a Cisco-managed bucket Cisco shows the key once when you set it up. For your own bucket: an IAM key with s3:ListBucket and s3:GetObject. |
| Secret access key | Stored encrypted and never shown again. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose Cisco Umbrella and Secure Access. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| DNS | dns | cisco_umbrella | cisco:cloud_security:dns | Every DNS query: identity, internal address, domain, category and whether it was blocked. |
| Web proxy | web | cisco_umbrella | cisco:cloud_security:proxy | Web requests through the secure web gateway: URL, category, verdict and file scans. |
| Cloud firewall | firewall | cisco_umbrella | cisco:cloud_security:firewall | Connections through the cloud firewall: source, destination, ports and verdict. |
| Intrusion prevention | network | cisco_umbrella | cisco:cloud_security:intrusion | Signatures the IPS matched, with severity, CVEs and the action taken. |
| Admin audit log | audit | cisco_umbrella | cisco:cloud_security:audit | Changes in the dashboard: who changed which policy or setting, before and after. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find Cisco Umbrella and Secure Access without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Network Resolution (DNS) | Queries with identity, domain, category and verdict. |
| Web | Requests with URL, category, verdict and file scan results. |
| Network Traffic | Firewall connections with source, destination, ports and verdict. |
| Intrusion Detection | IPS signatures with severity and CVEs. |
| Change | Dashboard changes with before and after. |
Field names follow the CIM field names. These are the fields LogPulse sets on Cisco Umbrella and Secure Access events; a field is left out when Cisco Umbrella and Secure Access did not send a value.
actionblocked_categorybytesbytes_inbytes_outcategorycvedestdest_hostdest_portdirectionfile_hashhttp_content_typehttp_methodhttp_referrerhttp_user_agentididentitiesobject_categoryqueryrecord_typereply_coderesultrule_idseveritysignaturesignature_idsrcsrc_portsrc_translated_ipstatustransporturluseruser_typevendor_action
The original record of Cisco Umbrella and Secure Access is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (dns, web, firewall, network, audit) source IN (cisco_umbrella)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| AWS refused the key. Check the access key and that it may list this bucket and prefix. | For a Cisco-managed bucket, rotate the key in Log Management and paste the new one. For your own bucket, give the IAM key s3:ListBucket and s3:GetObject. |
| The bucket is not in eu-central-1. | Fill in the region shown next to the bucket in Log Management. |
| No log folders (dnslogs, proxylogs, …) under the bucket root yet. | Check the data path: the folder before dnslogs/ and proxylogs/. Cisco writes a file every ten minutes per kind of log, so right after turning logging on there is nothing yet. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Cisco Umbrella and Secure Access may also simply have had nothing new. |
Frequently asked questions
- How do I send Cisco Umbrella and Secure Access logs to LogPulse?
- Add the Cisco Umbrella and Secure Access cloud integration under Configure, Sources, Cloud in LogPulse and fill in S3 bucket, Region, Access key ID, Secret access key. LogPulse reads the S3 log bucket (Cisco-managed or your own) itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in Cisco Umbrella and Secure Access?
- Logging to S3 turned on in Log Management. An access key that can list and read the bucket. Read access is enough for collecting logs.
- Which index does Cisco Umbrella and Secure Access data go to?
- The index is the kind of data: dns, web, firewall, network, audit. The source is the product: cisco_umbrella. Each data source has its own sourcetype, listed on this page.
- Which data models does Cisco Umbrella and Secure Access fill?
- Network Resolution (DNS), Web, Network Traffic, Intrusion Detection, Change. Detection rules and dashboards written for a data model work on Cisco Umbrella and Secure Access without changes.
- Does LogPulse delete the Umbrella log files?
- No. LogPulse lists and reads the files and never deletes them. Cisco or your own bucket lifecycle decides how long they stay.