Skip to content

Commit caae1dd

Browse files
Update designing-ztna-access-policies.mdx
1 parent a8924e7 commit caae1dd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -374,7 +374,7 @@ The first step is to configure an [egress IP policy under Cloudflare Gateway](/c
374374
| **Select Egress IP** | |
375375
| Use dedicated Cloudflare Egress IPs | \[203.0.113.88\] |
376376

377-
This is important not only for securing access to Salesforce, but also for adequately protecting its contents while in use. The next step is to examine the access policy. The policy is similar to the one we just created for the wiki. However, the policy is limiting access to members of the Sales or Executives groups. We are also using our Crowdstrike integration to ensure that users are on company managed devices.
377+
This is important not only for securing access to Salesforce, but also for adequately protecting its contents while in use. The next step is to examine the access policy which is similar to the one we just created for the wiki. However, this policy is limiting access to members of the Sales or Executives groups. We are also using our Crowdstrike integration to ensure that users are on company managed devices.
378378

379379
| Policy name | Account executives on trusted devices |
380380
| :----------------------------- | :------------------------------------ |

0 commit comments

Comments
 (0)