[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[[["\u003cp\u003eThis parser is designed to extract and map fields from Azion firewall JSON logs to the Unified Data Model (UDM) for Google SecOps.\u003c/p\u003e\n"],["\u003cp\u003eThe parser converts data types, enriches logs with details like user-agent parsing, and generates events such as NETWORK_HTTP, SCAN_UNCATEGORIZED, or GENERIC_EVENT, based on available principal and target machine data.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration involves setting up an Amazon S3 bucket, creating an IAM user with appropriate permissions, configuring Azion for continuous log delivery to S3, and setting up a feed in Google SecOps to ingest the logs from the bucket.\u003c/p\u003e\n"],["\u003cp\u003eThe parser maps various Azion log fields, such as \u003ccode\u003eremote_addr\u003c/code\u003e, \u003ccode\u003ehttp_user_agent\u003c/code\u003e, and \u003ccode\u003estatus\u003c/code\u003e, to their corresponding UDM fields, with specific logic for handling WAF-related data and determining security result actions.\u003c/p\u003e\n"],["\u003cp\u003eThe supported platform is Google SecOps and all features are under Pre-GA Offerings Terms of the Google Security Operations Service Specific Terms.\u003c/p\u003e\n"]]],[],null,["# Collect Azion firewall logs\n===========================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nOverview\n--------\n\nThis parser extracts fields from Azion firewall JSON logs, performs data type conversions and enrichment (for example, user-agent parsing), and maps the extracted fields to the UDM. It generates **NETWORK_HTTP** , **SCAN_UNCATEGORIZED** , or **GENERIC_EVENT** events based on the presence of principal and target machines. It also handles WAF-related fields and actions, mapping them to UDM security result fields.\n\nBefore you begin\n----------------\n\nEnsure that you have the following prerequisites:\n\n- Google SecOps instance.\n- Privileged access to AWS IAM and S3.\n- Privileged access to an active Azion account.\n\nConfigure Amazon S3 bucket\n--------------------------\n\n1. Create **Amazon S3 bucket** following this user guide: [Creating a bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html).\n2. Save bucket **Name** and **Region** for future reference.\n3. Create a **User** following this user guide: [Creating an IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html#id_users_create_console).\n4. Select the created **User**.\n5. Select **Security credentials** tab.\n6. Click **Create Access Key** in section **Access Keys**.\n7. Select **Third-party service** as **Use case**.\n8. Click **Next**.\n9. Optional: Add description tag.\n10. Click **Create access key**.\n11. Click **Download .csv file** . (Save **Access Key** and **Secret Access Key** for future reference).\n12. Click **Done**.\n13. Select **Permissions** tab.\n14. Click **Add permissions** in section **Permissions policies**.\n15. Select **Add permissions**.\n16. Select **Attach policies directly**.\n17. Search for **AmazonS3FullAccess** policy.\n18. Select the policy.\n19. Click **Next**.\n20. Click **Add permissions**.\n\nConfigure Azion for continuous log delivery to Amazon S3\n--------------------------------------------------------\n\n1. In the Azion console, go to to the **DataStream** section.\n2. Click **+ Stream**.\n3. Specify values for the following parameters:\n - **Name**: Provide a unique and descriptive name to identify the data stream.\n - **Source**: Select the source to collect the data from.\n - **Template**: A preset of variables for specific sources or an open template to choose variables. You have the option to filter domains.\n4. In **Destination** section, click **Connector** \\\u003e **Simple Storage Service (S3)** .\n - **URL** : the bucket URI. `s3:/BUCKET_NAME`. Replace the following:\n - `BUCKET_NAME`: the name of the bucket.\n - **Bucket Name**: Name of the bucket to which the object will be sent.\n - **Region**: Region where your bucket is located.\n - **Access Key**: User access key with access to the s3 bucket.\n - **Secret Key**: User secret key with access to the s3 bucket.\n - **Content Type**: Select plain/text.\n5. Click **Save**.\n\nFor more information, see [How to use Amazon S3 to receive data from Data Stream](https://www.azion.com/en/documentation/products/guides/endpoint-amazon-s3/)\n\nSet up feeds\n------------\n\nTo configure a feed, follow these steps:\n\n1. Go to **SIEM Settings** \\\u003e **Feeds**.\n2. Click **Add New Feed**.\n3. On the next page, click **Configure a single feed**.\n4. In the **Feed name** field, enter a name for the feed (for example, **Azion Logs**).\n5. Select **Amazon S3 V2** as the **Source type**.\n6. Select Azion as the **Log type**.\n7. Click **Next**.\n8. Specify values for the following input parameters:\n\n - **S3 URI** : the bucket URI.\n `s3:/BUCKET_NAME`.\n Replace the following:\n\n - `BUCKET_NAME`: the name of the bucket.\n - **Source deletion options**: select deletion option according to your preference.\n\n - **Maximum File Age** : Include files modified in the last number of days. Default is 180 days.\n Note: If you select the **Delete transferred files** or **Delete transferred files and empty directories** option, make sure that you granted appropriate permissions to the service account.\n\n - **Access Key ID**: the User access key with access to the s3 bucket.\n\n - **Secret Access Key**: the User secret key with access to the s3 bucket.\n\n - **Asset namespace** : the [asset namespace](/chronicle/docs/investigation/asset-namespaces).\n\n - **Ingestion labels**: the label to be applied to the events from this feed.\n\n9. Click **Next**.\n\n10. Review your new feed configuration in the **Finalize** screen, and then click **Submit**.\n\nUDM Mapping Table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]