Sumo Logic¶

Sumo Logic はクラウドネイティブなマシンデータ分析プラットフォームで、組織にIT運用、セキュリティ、アプリケーションパフォーマンスに関するリアルタイムの洞察を提供します。Wallarmを設定して、Sumo Logicにメッセージを送ることができます。

統合の設定¶

Sumo Logic UIで:

手順に従ってHosted Collectorを構成します。
手順に従ってHTTP Logs & Metrics Sourceを構成します。
提供された HTTP Source Address (URL) をコピーします。

Wallarm UIで:

Integrations セクションを開きます。
Sumo Logic ブロックをクリックするか、Add integration ボタンをクリックして Sumo Logic を選択します。
統合名を入力します。
コピーしたHTTP Source Address (URL) の値をHTTP Source Address (URL) フィールドに貼り付けます。
通知をトリガーするイベントタイプを選択します。

利用可能なイベントの詳細:
- Hits detected except for:
  - Experimental hits detected based on the custom regular expression. Non-experimental hits trigger notifications.
  - Hits not saved in the sample.
- System related:
  - User changes (newly created, deleted, role change)
  - Integration changes (disabled, deleted)
  - Application changes (newly created, deleted, name change)
  - Errors during regular update of specifications used for rogue API detection or API specification enforcement
- Vulnerabilities detected, all by default or only for the selected risk level(s) - high, medium or low.
- Rules and triggers changed (creating, updating, or deleting the rule or trigger)
- (Requires AASM Enterprise) Security issues detected, all or only for the selected risk level(s):
  - Critical risk
  - High risk
  - Medium risk
  - Low risk
  - Info risk
- On an hourly basis, you can get a notification with the number of requests processed during the previous hour

Test integration をクリックして、構成の正確性、Wallarm Cloudの利用可能性、通知フォーマットを確認します。

Sumologic通知のテスト:

{
    summary:"[テストメッセージ] [Test partner(US)] 新たな脆弱性が検出されました",
    description:"通知タイプ: vuln

                システムで新たな脆弱性が検出されました。

                ID: 
                タイトル: テスト
                ドメイン: example.com
                パス: 
                メソッド: 
                検出者: 
                パラメータ: 
                タイプ: 情報
                脅威: 中

                詳細: https://us1.my.wallarm.com/object/555


                クライアント: TestCompany
                Cloud: US
                ",
    details:{
        client_name:"TestCompany",
        cloud:"US",
        notification_type:"vuln",
        vuln_link:"https://us1.my.wallarm.com/object/555",
        vuln:{
            domain:"example.com",
            id:null,
            method:null,
            parameter:null,
            path:null,
            title:"テスト",
            discovered_by:null,
            threat:"中",
            type:"情報"
        }
    }
}

Add integration をクリックします。

Wallarm Cloud IP addresses

To provide Wallarm Cloud access to your system, you may need a list of its public IP addresses:

US CloudEU Cloud

35.235.66.155
34.102.90.100
34.94.156.115
35.235.115.105
34.94.85.217
34.94.51.234
34.102.59.122
34.94.238.72

34.141.230.156
34.91.138.113
34.90.114.134
35.204.127.78

追加のアラートの設定¶

Besides the notifications you have already set up through the integration card, Wallarm triggers allow you to select additional events for notifications:

Number of attacks, hits or incidents per time interval (day, hour, etc.) exceeds the set number
What is not counted
- For attacks:
  - The experimental attacks based on the custom regular expressions.
- For hits:
  - The experimental hits based on the custom regular expressions.
  - Hits not saved in the sample.
Changes in API took place
IP address was denylisted
New rogue API (shadow, orphan, zombie) was detected
New user was added to the company account

For condition detailing, you can add one or more filters. As soon, as condition and filters are set, select the integration through which the selected alert should be sent. You can select several integrations simultaneously.

統合の無効化と削除¶

You can delete or temporarily disable the integration. While deleting stops sending notificatioins and completely deletes all configuration, disabling just stops sending notifications which you can at any moment re-enable with the same settings.

If for the integration the System related events are selected to trigger notifications, Wallarm will notify about both of these actions.

システムの利用不可および統合パラメータの不正¶

Notifications to the system are sent via requests. If the system is unavailable or integration parameters are configured incorrectly, the error code is returned in the response to the request.

If the system responds to Wallarm request with any code other than 2xx, Wallarm resends the request with the interval until the 2xx code is received:

The first cycle intervals: 1, 3, 5, 10, 10 seconds
The second cycle intervals: 0, 1, 3, 5, 30 seconds
The third cycle intervals: 1, 1, 3, 5, 10, 30 minutes

If the percentage of unsuccessful requests reaches 60% in 12 hours, the integration is automatically disabled. If you receive system notifications, you will get a message about automatically disabled integration.