Skip to content

Commit 166936e

Browse files
Adding more info
1 parent 7cf1abe commit 166936e

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

src/content/docs/magic-firewall/how-to/enable-ids.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,8 +83,9 @@ Similarly, sending a patch request with the `enabled` field set to `true` will e
8383
IDS rules are run on a subset of packets. IDS also supports the current flows:
8484

8585
- Magic WAN to Magic WAN.
86-
- Magic Transit in both directions.
86+
- Magic Transit ingress traffic only when traffic is handled through direct server return.
87+
- Ingress and egress traffic when Magic Transit has the [Egress option enabled](/reference-architecture/architectures/magic-transit/#magic-transit-with-egress-option-enabled).
8788

8889
## Next steps
8990

90-
You must configure Logpush to log detected risks. Refer to [Configure a Logpush destination](/magic-firewall/how-to/use-logpush-with-ids/) for more information. Additionally, all traffic that is analyzed can be accessed via [network analytics](/analytics/network-analytics/). Refer to [GraphQL Analytics](/magic-firewall/tutorials/graphql-analytics/) to query the analytics data.
91+
You must configure Logpush to log detected risks. Refer to [Configure a Logpush destination](/magic-firewall/how-to/use-logpush-with-ids/) for more information. Additionally, all traffic that is analyzed can be accessed via [network analytics](/analytics/network-analytics/). Refer to [GraphQL Analytics](/magic-firewall/tutorials/graphql-analytics/) to query the analytics data.

0 commit comments

Comments
 (0)