Skip to content

W-18724314 xml threat protection flex #880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

glenn-rodgers-sf
Copy link
Contributor

Writer's Quality Checklist

Before merging your PR, did you:

  • Run spell checker
  • Run link checker to check for broken xrefs
  • Check for orphan files
  • Perform a local build and do a final visual check of your content, including checking for:
    • Broken images
    • Dead links
    • Correct rendering of partials if they are used in your content
    • Formatting issues, such as:
      • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
      • Messed up tables
      • Proper indentation
      • Correct header levels
  • Receive final review and signoff from:
    • Technical SME
    • Product Manager
    • Editor or peer reviewer
    • Reporter, if this content is in response to a reported issue (internal or external feedback)
  • If applicable, verify that the software actually got released

@glenn-rodgers-sf glenn-rodgers-sf requested review from marinasasso and a team as code owners June 10, 2025 17:36
@@ -117,6 +117,7 @@
*** xref:policies-outbound-oauth.adoc[Credential Injection OAuth 2.0]
*** xref:policies-outbound-circuit-breaker.adoc[Circuit Breaker Policy]
*** xref:policies-outbound-upstream-idle-timeout.adoc[Upstream Idle Timeout]
*** xref:policies-included-xml-threat-protection.adoc[XML Threat Protection]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid hard-coding titles unless you're changing them from the H1 text.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We hard code them because the policy titles have "Policy" in them and we remove it from the left nav.


[width="100%", cols="1,3"]
|===
>s|Policy Name| XML Threat Protection
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've never seen this format!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why, but all of our policies use it.


== Summary

Applications processing XML requests are susceptible to attacks characterized by unusual inflation of elements, attributes, and deep nesting levels. Attackers use recursive techniques to consume memory resources. Dramatic increases in the size of the application data often signal a security risk. Use the XML Threat Protection policy to reject unusual requests that exceed the defined expected size.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hard to parse (had to read twice). Suggest "Applications that process..."


[%header%autowidth.spread,cols="a,a"]
|===
|Field |Description
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a move away from using tables for two-column info.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use this in all of our policies, so I'd rather reformat them as a whole then just this one.


[%header%autowidth.spread,cols="a,a,a,a"]
|===
|Parameter | Required or Optional | Default Value | Description
Copy link
Contributor

@hannanelson hannanelson Jun 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typically, we use "Required" in the column heading and then "Yes" or "No" in the row.

@@ -101,7 +101,7 @@ endif::[]

| Upstream Idle Timeout ^| xref:gateway::policies-outbound-upstream-idle-timeout.adoc[✓] ^| | | Sets the maximum duration a stream between Flex Gateway and an upstream service can remain idle
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid checkmarks. See CX Table guidelines.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar here, I'm willing to move away from this, but can't handle it in this pr.

@glenn-rodgers-sf glenn-rodgers-sf merged commit d016b78 into flex-1-10-release Jun 10, 2025
4 checks passed
@glenn-rodgers-sf glenn-rodgers-sf deleted the W-18724314-xml-threat-protection-flex branch June 10, 2025 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants