{ "name": "symantec_endpoint_security", "title": "Symantec Endpoint Security", "version": "1.10.0", "release": "ga", "description": "Collect logs from Symantec Endpoint Security with Elastic Agent.", "type": "integration", "download": "/epr/symantec_endpoint_security/symantec_endpoint_security-1.10.0.zip", "path": "/package/symantec_endpoint_security/1.10.0", "icons": [ { "src": "/img/symantec-logo.svg", "path": "/package/symantec_endpoint_security/1.10.0/img/symantec-logo.svg", "title": "Sample logo", "size": "32x32", "type": "image/svg+xml" } ], "conditions": { "kibana": { "version": "^8.16.5 || ^9.0.0" }, "elastic": { "subscription": "basic" } }, "owner": { "type": "elastic", "github": "elastic/security-service-integrations" }, "categories": [ "security", "edr_xdr" ], "signature_path": "/epr/symantec_endpoint_security/symantec_endpoint_security-1.10.0.zip.sig", "format_version": "3.0.3", "readme": "/package/symantec_endpoint_security/1.10.0/docs/README.md", "license": "basic", "screenshots": [ { "src": "/img/ses-threat-and-user.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-threat-and-user.png", "title": "Threat and User Dashboard", "size": "600x600", "type": "image/png" }, { "src": "/img/ses-security-event.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-security-event.png", "title": "Security Event Dashboard", "size": "600x600", "type": "image/png" }, { "src": "/img/ses-container-module-and-kernel.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-container-module-and-kernel.png", "title": "Container, Module and Kernel Dashboard", "size": "600x600", "type": "image/png" }, { "src": "/img/ses-file-email-and-entity.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-file-email-and-entity.png", "title": "File, Email and Entity Dashboard", "size": "600x600", "type": "image/png" }, { "src": "/img/ses-overview.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-overview.png", "title": "Overview Dashboard", "size": "600x600", "type": "image/png" }, { "src": "/img/ses-system-application-and-audit-event.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-system-application-and-audit-event.png", "title": "System Application and Audit Event Dashboard", "size": "600x600", "type": "image/png" }, { "src": "/img/ses-incident.png", "path": "/package/symantec_endpoint_security/1.10.0/img/ses-incident.png", "title": "EDR Incident Dashboard", "size": "600x600", "type": "image/png" } ], "assets": [ "/package/symantec_endpoint_security/1.10.0/LICENSE.txt", "/package/symantec_endpoint_security/1.10.0/changelog.yml", "/package/symantec_endpoint_security/1.10.0/manifest.yml", "/package/symantec_endpoint_security/1.10.0/validation.yml", "/package/symantec_endpoint_security/1.10.0/docs/README.md", "/package/symantec_endpoint_security/1.10.0/img/ses-container-module-and-kernel.png", "/package/symantec_endpoint_security/1.10.0/img/ses-file-email-and-entity.png", "/package/symantec_endpoint_security/1.10.0/img/ses-incident.png", "/package/symantec_endpoint_security/1.10.0/img/ses-overview.png", "/package/symantec_endpoint_security/1.10.0/img/ses-security-event.png", "/package/symantec_endpoint_security/1.10.0/img/ses-system-application-and-audit-event.png", "/package/symantec_endpoint_security/1.10.0/img/ses-threat-and-user.png", "/package/symantec_endpoint_security/1.10.0/img/symantec-logo.svg", "/package/symantec_endpoint_security/1.10.0/data_stream/event/manifest.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/sample_event.json", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/manifest.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/sample_event.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-2926c4d6-8bd4-4591-b16f-9a2fe92d9537.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-307802ca-681c-42d5-9518-93d8cb3f9cc6.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-48a8e233-f36c-4acb-99f2-c348c6781f6f.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-8f4d2ce2-c5f2-421f-be7b-ffde36b86a0f.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-a1361bd2-d3ef-4ee3-8dfa-4930bb91be4a.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-bfbe8f7e-74af-4f0e-9037-793baa3709d5.json", "/package/symantec_endpoint_security/1.10.0/kibana/dashboard/symantec_endpoint_security-ca452d05-b541-49e3-aa31-61d619188235.json", "/package/symantec_endpoint_security/1.10.0/kibana/search/symantec_endpoint_security-fcfc6277-7973-4116-8358-a20c3d8f7663.json", "/package/symantec_endpoint_security/1.10.0/kibana/tag/symantec_endpoint_security-security-solution-default.json", "/package/symantec_endpoint_security/1.10.0/data_stream/event/fields/base-fields.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/fields/beats.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/fields/fields.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/fields/base-fields.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/fields/beats.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/fields/fields.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/agent/stream/abs.yml.hbs", "/package/symantec_endpoint_security/1.10.0/data_stream/event/agent/stream/aws-s3.yml.hbs", "/package/symantec_endpoint_security/1.10.0/data_stream/event/agent/stream/gcs.yml.hbs", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/default.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_category_application.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_category_audit.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_category_diagnostic.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_category_license.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_category_security.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_category_system.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_actor.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_attack.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_connection.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_container.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_cybox.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_device.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_file.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_kernel.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_license.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_module.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_parent.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_policy.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_process.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_registry.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_session.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_source.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_threat.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/event/elasticsearch/ingest_pipeline/pipeline_object_user.yml", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/agent/stream/cel.yml.hbs", "/package/symantec_endpoint_security/1.10.0/data_stream/incident/elasticsearch/ingest_pipeline/default.yml" ], "policy_templates": [ { "name": "Symantec Endpoint Security", "title": "Symantec Endpoint Security logs", "description": "Collect logs using AWS S3, AWS SQS or Azure Blob Storage.", "inputs": [ { "type": "cel", "vars": [ { "name": "client_id", "type": "text", "title": "Client ID", "description": "Client ID for the Symantec Endpoint Security.", "multi": false, "required": true, "show_user": true }, { "name": "client_secret", "type": "password", "title": "Client Secret", "description": "Client Secret for the Symantec Endpoint Security.", "multi": false, "required": true, "show_user": true }, { "name": "url", "type": "text", "title": "URL", "description": "Base URL of the Symantec Endpoint Security API.", "multi": false, "required": true, "show_user": true, "default": "https://api.sep.securitycloud.symantec.com" }, { "name": "token_url", "type": "text", "title": "Token URL", "description": "Token URL of Symantec Endpoint Security.", "multi": false, "required": true, "show_user": false, "default": "https://api.sep.securitycloud.symantec.com/v1/oauth2/tokens" }, { "name": "proxy_url", "type": "text", "title": "Proxy URL", "description": "URL to proxy connections in the form of http[s]://:@:. Please ensure your username and password are in URL encoded format.", "multi": false, "required": false, "show_user": false }, { "name": "ssl", "type": "yaml", "title": "SSL Configuration", "description": "SSL configuration options. See [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-ssl.html#ssl-common-config) for details.", "multi": false, "required": false, "show_user": false, "default": "#certificate_authorities:\n# - |\n# -----BEGIN CERTIFICATE-----\n# MIIDCjCCAfKgAwIBAgITJ706Mu2wJlKckpIvkWxEHvEyijANBgkqhkiG9w0BAQsF\n# ADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwIBcNMTkwNzIyMTkyOTA0WhgPMjExOTA2\n# MjgxOTI5MDRaMBQxEjAQBgNVBAMMCWxvY2FsaG9zdDCCASIwDQYJKoZIhvcNAQEB\n# BQADggEPADCCAQoCggEBANce58Y/JykI58iyOXpxGfw0/gMvF0hUQAcUrSMxEO6n\n# fZRA49b4OV4SwWmA3395uL2eB2NB8y8qdQ9muXUdPBWE4l9rMZ6gmfu90N5B5uEl\n# 94NcfBfYOKi1fJQ9i7WKhTjlRkMCgBkWPkUokvBZFRt8RtF7zI77BSEorHGQCk9t\n# /D7BS0GJyfVEhftbWcFEAG3VRcoMhF7kUzYwp+qESoriFRYLeDWv68ZOvG7eoWnP\n# PsvZStEVEimjvK5NSESEQa9xWyJOmlOKXhkdymtcUd/nXnx6UTCFgnkgzSdTWV41\n# CI6B6aJ9svCTI2QuoIq2HxX/ix7OvW1huVmcyHVxyUECAwEAAaNTMFEwHQYDVR0O\n# BBYEFPwN1OceFGm9v6ux8G+DZ3TUDYxqMB8GA1UdIwQYMBaAFPwN1OceFGm9v6ux\n# 8G+DZ3TUDYxqMA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAG5D\n# 874A4YI7YUwOVsVAdbWtgp1d0zKcPRR+r2OdSbTAV5/gcS3jgBJ3i1BN34JuDVFw\n# 3DeJSYT3nxy2Y56lLnxDeF8CUTUtVQx3CuGkRg1ouGAHpO/6OqOhwLLorEmxi7tA\n# H2O8mtT0poX5AnOAhzVy7QW0D/k4WaoLyckM5hUa6RtvgvLxOwA0U+VGurCDoctu\n# 8F4QOgTAWyh8EZIwaKCliFRSynDpv3JTUwtfZkxo6K6nce1RhCWFAsMvDZL8Dgc0\n# yvgJ38BRsFOtkRuAGSf6ZUwTO8JJRRIFnpUzXflAnGivK9M13D5GEQMmIl6U9Pvk\n# sxSmbIUfc2SGJGCJD4I=\n# -----END CERTIFICATE-----\n" } ], "title": "Collect EDR Incidents via API", "description": "Collecting EDR Incidents logs via API." }, { "type": "aws-s3", "title": "Collect Symantec Endpoint Security logs via AWS S3 or AWS SQS", "description": "Collecting logs from Symantec Endpoint Security via AWS S3 or AWS SQS." }, { "type": "gcs", "title": "Collect Symantec Endpoint Security logs via GCS (Google Cloud Storage)", "description": "Collect JSON data from configured GCS Bucket with Elastic Agent." }, { "type": "azure-blob-storage", "title": "Collect Symantec Endpoint Security logs via Azure Blob Storage", "description": "Collect JSON data from configured Azure Blob Storage Container with Elastic Agent." } ], "multiple": true } ], "data_streams": [ { "type": "logs", "dataset": "symantec_endpoint_security.event", "title": "Symantec Endpoint Security Event", "release": "ga", "ingest_pipeline": "default", "streams": [ { "input": "aws-s3", "vars": [ { "name": "collect_s3_logs", "type": "bool", "title": "Collect logs via S3 Bucket", "description": "To collect logs via S3 bucket enable the toggle switch. By default, it will collect logs via SQS Queue.", "multi": false, "required": true, "show_user": true, "default": false }, { "name": "bucket_arn", "type": "text", "title": "[S3] Bucket ARN", "description": "ARN of the AWS S3 bucket that will be polled for list operation. It is a required parameter for collecting logs via the AWS S3 Bucket unless you set an Access Point ARN. In case both configurations are added, this one takes precedence.", "multi": false, "required": false, "show_user": true }, { "name": "access_point_arn", "type": "text", "title": "[S3] Access Point ARN", "description": "ARN of the AWS S3 Access Point that will be polled for list operation. Mandatory if the \"Collect logs via S3 Bucket\" switch is on. It is a required parameter for collecting logs via the AWS S3 Bucket unless you set a Bucket ARN.", "multi": false, "required": false, "show_user": true }, { "name": "queue_url", "type": "text", "title": "[SQS] Queue URL", "description": "URL of the AWS SQS queue that messages will be received from. It is a required parameter for collecting logs via the AWS SQS.", "multi": false, "required": false, "show_user": true }, { "name": "access_key_id", "type": "password", "title": "Access Key ID", "description": "First part of access key. This parameter along with the secret_access_key parameter is required if we are not providing shared_credential_file.", "multi": false, "required": false, "show_user": true }, { "name": "secret_access_key", "type": "password", "title": "Secret Access Key", "description": "Second part of access key. This parameter along with the access_key_id parameter is required if we are not providing shared_credential_file.", "multi": false, "required": false, "show_user": true }, { "name": "session_token", "type": "password", "title": "Session Token", "description": "Required when using temporary security credentials.", "multi": false, "required": false, "show_user": true }, { "name": "shared_credential_file", "type": "text", "title": "Shared Credential File", "description": "Directory of the shared credentials file. This parameter is required if we are not providing value for the parameters - secret_access_key and access_key_id.", "multi": false, "required": false, "show_user": false }, { "name": "credential_profile_name", "type": "text", "title": "Credential Profile Name", "description": "Profile name in shared credentials file.", "multi": false, "required": false, "show_user": false }, { "name": "role_arn", "type": "text", "title": "Role ARN", "description": "AWS IAM Role to assume.", "multi": false, "required": false, "show_user": false }, { "name": "region", "type": "text", "title": "[SQS] Region", "description": "The name of the AWS region of the end point. If this option is given it takes precedence over the region name obtained from the queue_url value.", "multi": false, "required": false, "show_user": true }, { "name": "fips_enabled", "type": "bool", "title": "Enable S3 FIPS", "description": "Enabling this option changes the service name from `s3` to `s3-fips` for connecting to the correct service endpoint.", "multi": false, "required": false, "show_user": false, "default": false }, { "name": "proxy_url", "type": "text", "title": "Proxy URL", "description": "URL to proxy connections in the form of http[s]://:@:. Please ensure your username and password are in URL encoded format.", "multi": false, "required": false, "show_user": false }, { "name": "bucket_list_prefix", "type": "text", "title": "[S3] Bucket Prefix", "description": "Prefix to apply for the list request to the S3 bucket.", "multi": false, "required": false, "show_user": true }, { "name": "interval", "type": "text", "title": "[S3] Interval", "description": "Time interval for polling listing of the S3 bucket. NOTE: Supported units are h/m/s.", "multi": false, "required": false, "show_user": true, "default": "3m" }, { "name": "number_of_workers", "type": "integer", "title": "[S3] Number of Workers", "description": "Number of workers that will process the S3 objects listed.", "multi": false, "required": false, "show_user": true, "default": 5 }, { "name": "start_timestamp", "type": "text", "title": "[S3] Start Timestamp", "description": "If set, only read S3 objects with last modified timestamp newer than the given timestamp. Accepts a timestamp in `YYYY-MM-DDTHH:MM:SSZ` format. For example, \"2020-10-10T10:30:00Z\" (UTC) or \"2020-10-10T10:30:00Z+02:30\" (with zone offset).", "multi": false, "required": false, "show_user": false }, { "name": "ignore_older", "type": "text", "title": "[S3] Ignore Older Timespan", "description": "If set, ignore S3 objects whose Last-Modified time is before the ignore older timespan. Timespan is checked from the current time to S3 object's Last-Modified time. Accepts a duration like `48h`, `2h30m`.", "multi": false, "required": false, "show_user": false }, { "name": "visibility_timeout", "type": "text", "title": "[SQS] Visibility Timeout", "description": "The duration that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request. The maximum is 12 hours. NOTE: Supported units for this parameter are h/m/s.", "multi": false, "required": false, "show_user": true, "default": "300s" }, { "name": "api_timeout", "type": "text", "title": "[SQS] API Timeout", "description": "The maximum duration of AWS API can take. The maximum is half of the visibility timeout value. NOTE: Supported units for this parameter are h/m/s.", "multi": false, "required": false, "show_user": true, "default": "120s" }, { "name": "max_number_of_messages", "type": "integer", "title": "[SQS] Maximum Concurrent SQS Messages", "description": "The maximum number of SQS messages that can be inflight at any time.", "multi": false, "required": false, "show_user": true, "default": 5 }, { "name": "file_selectors", "type": "yaml", "title": "[SQS] File Selectors", "description": "If the SQS queue will have events that correspond to files that this integration shouldn’t process, file_selectors can be used to limit the files that are downloaded. This is a list of selectors which are made up of regex and expand_event_list_from_field options. The regex should match the S3 object key in the SQS message, and the optional expand_event_list_from_field is the same as the global setting. If file_selectors is given, then any global expand_event_list_from_field value is ignored in favor of the ones specified in the file_selectors. Regexes use [RE2 syntax](https://pkg.go.dev/regexp/syntax). Files that don’t match one of the regexes will not be processed.", "multi": false, "required": false, "show_user": false, "default": "# - regex: \"event/\"\n" }, { "name": "tags", "type": "text", "title": "Tags", "multi": true, "required": true, "show_user": false, "default": [ "forwarded", "symantec_endpoint_security-event" ] }, { "name": "preserve_original_event", "type": "bool", "title": "Preserve original event", "description": "Preserves a raw copy of the original event, added to the field `event.original`.", "multi": false, "required": false, "show_user": true, "default": false }, { "name": "preserve_duplicate_custom_fields", "type": "bool", "title": "Preserve duplicate custom fields", "description": "Preserve symantec_endpoint_security.event fields that were copied to Elastic Common Schema (ECS) fields.", "multi": false, "required": false, "show_user": false, "default": false }, { "name": "processors", "type": "yaml", "title": "Processors", "description": "Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This executes in the agent before the logs are parsed. See [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.", "multi": false, "required": false, "show_user": false }, { "name": "ssl", "type": "yaml", "title": "SSL Configuration", "description": "SSL configuration options. See [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-ssl.html#ssl-common-config) for details.", "multi": false, "required": false, "show_user": false, "default": "#certificate_authorities:\n# - |\n# -----BEGIN CERTIFICATE-----\n# MIIDCjCCAfKgAwIBAgITJ706Mu2wJlKckpIvkWxEHvEyijANBgkqhkiG9w0BAQsF\n# ADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwIBcNMTkwNzIyMTkyOTA0WhgPMjExOTA2\n# MjgxOTI5MDRaMBQxEjAQBgNVBAMMCWxvY2FsaG9zdDCCASIwDQYJKoZIhvcNAQEB\n# BQADggEPADCCAQoCggEBANce58Y/JykI58iyOXpxGfw0/gMvF0hUQAcUrSMxEO6n\n# fZRA49b4OV4SwWmA3395uL2eB2NB8y8qdQ9muXUdPBWE4l9rMZ6gmfu90N5B5uEl\n# 94NcfBfYOKi1fJQ9i7WKhTjlRkMCgBkWPkUokvBZFRt8RtF7zI77BSEorHGQCk9t\n# /D7BS0GJyfVEhftbWcFEAG3VRcoMhF7kUzYwp+qESoriFRYLeDWv68ZOvG7eoWnP\n# PsvZStEVEimjvK5NSESEQa9xWyJOmlOKXhkdymtcUd/nXnx6UTCFgnkgzSdTWV41\n# CI6B6aJ9svCTI2QuoIq2HxX/ix7OvW1huVmcyHVxyUECAwEAAaNTMFEwHQYDVR0O\n# BBYEFPwN1OceFGm9v6ux8G+DZ3TUDYxqMB8GA1UdIwQYMBaAFPwN1OceFGm9v6ux\n# 8G+DZ3TUDYxqMA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAG5D\n# 874A4YI7YUwOVsVAdbWtgp1d0zKcPRR+r2OdSbTAV5/gcS3jgBJ3i1BN34JuDVFw\n# 3DeJSYT3nxy2Y56lLnxDeF8CUTUtVQx3CuGkRg1ouGAHpO/6OqOhwLLorEmxi7tA\n# H2O8mtT0poX5AnOAhzVy7QW0D/k4WaoLyckM5hUa6RtvgvLxOwA0U+VGurCDoctu\n# 8F4QOgTAWyh8EZIwaKCliFRSynDpv3JTUwtfZkxo6K6nce1RhCWFAsMvDZL8Dgc0\n# yvgJ38BRsFOtkRuAGSf6ZUwTO8JJRRIFnpUzXflAnGivK9M13D5GEQMmIl6U9Pvk\n# sxSmbIUfc2SGJGCJD4I=\n# -----END CERTIFICATE-----\n" } ], "template_path": "aws-s3.yml.hbs", "title": "Event logs", "description": "Collect Symantec Endpoint Security logs via AWS S3 input.", "enabled": false, "ingestion_method": "AWS S3" }, { "input": "gcs", "vars": [ { "name": "project_id", "type": "text", "title": "Project ID", "description": "It is a required parameter to collect logs via GCS.", "multi": false, "required": true, "show_user": true, "default": "my-project-id" }, { "name": "service_account_key", "type": "password", "title": "Service Account Key", "description": "The json service account credentials string, which can be generated from the google cloud console, ref [Service Account Keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys).\nThis should be the entire JSON object that is present in the credentials.json file. Required if a Service Account Credentials File is not provided.\n", "multi": false, "required": false, "show_user": true }, { "name": "service_account_file", "type": "text", "title": "Service Account Credentials File", "description": "Path to a file containing the service account key text to authenticate to the data store, which can be generated from the google cloud console, ref [Service Account Keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys).\nRequired if a Service Account Key is not provided.\n", "multi": false, "required": false, "show_user": true }, { "name": "number_of_workers", "type": "integer", "title": "Maximum number of workers", "description": "Determines how many workers are spawned per bucket.", "multi": false, "required": false, "show_user": true, "default": 3 }, { "name": "poll", "type": "bool", "title": "Polling", "description": "Determines if the bucket will be continuously polled for new documents.", "multi": false, "required": false, "show_user": true, "default": true }, { "name": "poll_interval", "type": "text", "title": "Polling interval", "description": "Determines the time interval between polling operations.", "multi": false, "required": false, "show_user": true, "default": "15s" }, { "name": "bucket_timeout", "type": "text", "title": "Bucket Timeout", "description": "Defines the maximum time that the sdk will wait for a bucket api response before timing out. Valid time units are ns, us, ms, s, m, h.", "multi": false, "required": false, "show_user": true, "default": "120s" }, { "name": "buckets", "type": "yaml", "title": "Buckets", "description": "This attribute contains the details about a specific bucket like name, max_workers, poll, poll_interval and bucket_timeout. The attribute name is specific to a bucket as it describes the bucket name, while the fields max_workers, poll, poll_interval and bucket_timeout can exist both at the bucket level and the root level. \nIt is internally represented as an array, so multiple buckets can be provided.\nFor more information about each attribute, please see the relevant [Documentation](https://www.elastic.co/guide/en/beats/filebeat/8.5/filebeat-input-gcs.html#attrib-buckets).\n", "multi": false, "required": true, "show_user": true, "default": "# You can define as many buckets as you want here.\n\n- name: event_logs\n- name: event_logs_2\n\n# The config below is an example of how to override the global config.\n\n#- name: event_logs_3\n# number_of_workers: 3\n# poll: true\n# poll_interval: 10s\n# bucket_timeout: 30s\n" }, { "name": "file_selectors", "type": "yaml", "title": "[GCS] File Selectors", "description": "If the GCS bucket will have events that correspond to files that this integration shouldn’t process, file_selectors can be used to limit the files that are downloaded. This is a list of selectors which is made up of regex patters. The regex should match the GCS bucket filepath. Regexes use [RE2 syntax](https://pkg.go.dev/regexp/syntax). Files that don’t match one of the regexes will not be processed.", "multi": false, "required": false, "show_user": false, "default": "# - regex: \"event/\"\n" }, { "name": "timestamp_epoch", "type": "integer", "title": "Timestamp Epoch", "description": "Defines the epoch time in seconds, which is used to filter out objects/files that are older than the specified timestamp.", "multi": false, "required": false, "show_user": false }, { "name": "preserve_original_event", "type": "bool", "title": "Preserve original event", "description": "Preserves a raw copy of the original event, added to the field `event.original`.", "multi": false, "required": false, "show_user": true, "default": false }, { "name": "preserve_duplicate_custom_fields", "type": "bool", "title": "Preserve duplicate custom fields", "description": "Preserve symantec_endpoint_security.event fields that were copied to Elastic Common Schema (ECS) fields.", "multi": false, "required": false, "show_user": false, "default": false }, { "name": "processors", "type": "yaml", "title": "Processors", "description": "Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This executes in the agent before the logs are parsed. See [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.\n", "multi": false, "required": false, "show_user": false }, { "name": "tags", "type": "text", "title": "Tags", "multi": true, "required": true, "show_user": false, "default": [ "forwarded", "symantec_endpoint_security-event" ] } ], "template_path": "gcs.yml.hbs", "title": "Event logs", "description": "Collect Symantec Endpoint Security logs via GCS input.", "enabled": false, "ingestion_method": "Google Cloud Storage" }, { "input": "azure-blob-storage", "vars": [ { "name": "account_name", "type": "text", "title": "Account Name", "description": "This attribute is required for various internal operations with respect to authentication, creating service clients and blob clients which are used internally for various processing purposes.\n", "multi": false, "required": true, "show_user": true }, { "name": "service_account_key", "type": "password", "title": "Service Account Key", "description": "This attribute contains the access key, found under the Access keys section on Azure Cloud, under the respective storage account. A single storage account can contain multiple containers, and they will all use this common access key.\n", "multi": false, "required": false, "show_user": true }, { "name": "service_account_uri", "type": "text", "title": "Service Account URI", "description": "This attribute contains the connection string, found under the Access keys section on Azure Cloud, under the respective storage account. A single storage account can contain multiple containers, and they will all use this common connection string.\n", "multi": false, "required": false, "show_user": false }, { "name": "storage_url", "type": "text", "title": "Storage URL", "description": "Use this attribute to specify a custom storage URL if required. By default it points to azure cloud storage. Only use this if there is a specific need to connect to a different environment where blob storage is available.\nURL format : {{protocol}}://{{account_name}}.{{storage_uri}}.\n", "multi": false, "required": false, "show_user": false }, { "name": "number_of_workers", "type": "integer", "title": "Maximum number of workers", "description": "Determines how many workers are spawned per container.", "multi": false, "required": false, "show_user": true, "default": 10 }, { "name": "poll", "type": "bool", "title": "Polling", "description": "Determines if the container will be continuously polled for new documents.", "multi": false, "required": false, "show_user": true, "default": true }, { "name": "poll_interval", "type": "text", "title": "Polling interval", "description": "Determines the time interval between polling operations.", "multi": false, "required": false, "show_user": true, "default": "1m" }, { "name": "containers", "type": "yaml", "title": "Containers", "description": "This attribute contains the details about a specific container like, name, number_of_workers, poll, poll_interval etc. The attribute 'name' is specific to a container as it describes the container name, while the fields number_of_workers, poll, poll_interval can exist both at the container level and at the global level. If you have already defined the attributes globally, then you can only specify the container name in this yaml config. If you want to override any specific attribute for a container, then, you can define it here. Any attribute defined in the yaml will override the global definitions. Please see the relevant [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-azure-blob-storage.html#attrib-containers) for further information.\n", "multi": false, "required": true, "show_user": true, "default": "# - name: azure-container1\n# max_workers: 3\n# poll: true\n# poll_interval: 15s\n# timestamp_epoch: 1630444800\n# - name: azure-container2\n# max_workers: 3\n# poll: true\n# poll_interval: 10s\n# timestamp_epoch: 1630444800\n" }, { "name": "file_selectors", "type": "yaml", "title": "File Selectors", "description": "If the container will have events that correspond to files that this integration shouldn’t process, file_selectors can be used to limit the files that are downloaded. This is a list of selectors which is made up of regex patters. The regex should match the container filepath. Regexes use [RE2 syntax](https://pkg.go.dev/regexp/syntax). Files that don’t match one of the regexes will not be processed.\n", "multi": false, "required": false, "show_user": false, "default": "# - regex: \"event/\"\n" }, { "name": "timestamp_epoch", "type": "integer", "title": "Timestamp Epoch", "description": "This attribute can be used to filter out files/blobs which have a timestamp older than the specified value. The value of this attribute should be in unix epoch (seconds) format.\n", "multi": false, "required": false, "show_user": false }, { "name": "expand_event_list_from_field", "type": "text", "title": "Expand Event List From Field", "description": "If the file-set using this input expects to receive multiple messages bundled under a specific field or an array of objects then the config option for 'expand_event_list_from_field' can be specified. This setting will be able to split the messages under the group value into separate events. This can be specified at the global level or at the container level. For more info please refer to the [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-azure-blob-storage.html#attrib-expand_event_list_from_field).\n", "multi": false, "required": false, "show_user": false }, { "name": "preserve_original_event", "type": "bool", "title": "Preserve original event", "description": "Preserves a raw copy of the original event, added to the field `event.original`", "multi": false, "required": false, "show_user": true, "default": false }, { "name": "preserve_duplicate_custom_fields", "type": "bool", "title": "Preserve duplicate custom fields", "description": "Preserve symantec_endpoint_security.event fields that were copied to Elastic Common Schema (ECS) fields.", "multi": false, "required": false, "show_user": false, "default": false }, { "name": "processors", "type": "yaml", "title": "Processors", "description": "Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This executes in the agent before the logs are parsed. See [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.\n", "multi": false, "required": false, "show_user": false }, { "name": "tags", "type": "text", "title": "Tags", "description": "Tags to include in the published event", "multi": true, "required": false, "show_user": true, "default": [ "forwarded", "symantec_endpoint_security-event" ] } ], "template_path": "abs.yml.hbs", "title": "Event logs", "description": "Collect Symantec Endpoint Security logs via Azure Blob Storage input.", "enabled": false, "ingestion_method": "Azure Blob Storage" } ], "package": "symantec_endpoint_security", "path": "event" }, { "type": "logs", "dataset": "symantec_endpoint_security.incident", "title": "Collect Incident logs from Symantec Endpoint Security", "release": "ga", "ingest_pipeline": "default", "streams": [ { "input": "cel", "vars": [ { "name": "initial_interval", "type": "text", "title": "Initial Interval", "description": "How far back to pull the Incident logs from Symantec Endpoint Security. Supported units for this parameter are h/m/s. Initial Interval cannot be older than 30 days.", "multi": false, "required": true, "show_user": true, "default": "24h" }, { "name": "interval", "type": "text", "title": "Interval", "description": "Duration between requests to the Incident API. Supported units for this parameter are h/m/s.", "multi": false, "required": true, "show_user": true, "default": "1m" }, { "name": "batch_size", "type": "integer", "title": "Batch Size", "description": "Batch size for the response of the Incident API. The maximum supported batch size value is 2000.", "multi": false, "required": true, "show_user": false, "default": 2000 }, { "name": "http_client_timeout", "type": "text", "title": "HTTP Client Timeout", "description": "Duration before declaring that the HTTP client connection has timed out. Valid time units are ns, us, ms, s, m, h.", "multi": false, "required": true, "show_user": false, "default": "30s" }, { "name": "enable_request_tracer", "type": "bool", "title": "Enable request tracing", "description": "The request tracer logs requests and responses to the agent's local file-system for debugging configurations. Enabling this request tracing compromises security and should only be used for debugging. Disabling the request tracer will delete any stored traces. See [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-cel.html#_resource_tracer_enable) for details.", "multi": false, "required": false, "show_user": false }, { "name": "tags", "type": "text", "title": "Tags", "multi": true, "required": true, "show_user": false, "default": [ "forwarded", "ses-incident" ] }, { "name": "preserve_original_event", "type": "bool", "title": "Preserve original event", "description": "Preserves a raw copy of the original event, added to the field `event.original`.", "multi": false, "required": true, "show_user": true, "default": false }, { "name": "preserve_duplicate_custom_fields", "type": "bool", "title": "Preserve duplicate custom fields", "description": "Preserve ses.incident fields that were copied to Elastic Common Schema (ECS) fields.", "multi": false, "required": true, "show_user": false, "default": false }, { "name": "processors", "type": "yaml", "title": "Processors", "description": "Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This executes in the agent before the logs are parsed. See [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.", "multi": false, "required": false, "show_user": false } ], "template_path": "cel.yml.hbs", "title": "Incident logs", "description": "Collect Incident logs from Symantec Endpoint Security.", "enabled": false, "ingestion_method": "API" } ], "package": "symantec_endpoint_security", "path": "incident" } ] }