Skip to content

Conversation

kingthorin
Copy link
Member

Potential Images zapbot_split_1_nobg zapbot_split_2_nobg

@psiinon
Copy link
Member

psiinon commented Jul 18, 2025

Logo
Checkmarx One – Scan Summary & Details4a05d1df-8a53-421e-a3dc-49e2167c4eee

Great job, no security vulnerabilities found in this Pull Request

@kingthorin kingthorin force-pushed the split-blog branch 3 times, most recently from 3dad00e to ee1424f Compare July 20, 2025 21:04
@kingthorin kingthorin force-pushed the split-blog branch 2 times, most recently from afcac9a to 40f8d28 Compare July 21, 2025 10:07
![ZAPbot with Edge browser icon](images/blog-edge.png)

These changes were made to provide users with greater flexibility in creating scan policies.
In the last few years a number of changes have been implemented to address the potential for false positives.¹
Copy link
Member

Choose a reason for hiding this comment

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

These 2 statements dont really seem to flow for me :/

Copy link
Member Author

Choose a reason for hiding this comment

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

I left it just with the first statement. Put the superscript 1 marks on the two rules themselves, and re-jigged the footnote a bit.


#### Alert Tag TEST_TIMING

The rules (and alerts) are now also decorated with the [TEST_TIMING](/alerttags/test_timing/)[Alert Tag](/docs/desktop/ui/dialogs/addalert/#alert-tags).
Copy link
Member

Choose a reason for hiding this comment

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

Needs a space between TEST_Timing & Alert Tag. TBH Not sure the 2nd link is needed..

Copy link
Member Author

Choose a reason for hiding this comment

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

Done & done


The rules (and alerts) are now also decorated with the [TEST_TIMING](/alerttags/test_timing/)[Alert Tag](/docs/desktop/ui/dialogs/addalert/#alert-tags).

### New Passive Scan Rule - ZAP is Out of Date
Copy link
Member

Choose a reason for hiding this comment

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

I'm now having second thoughts about including this - it doesnt seem to be releated to the rest of the post?

Copy link
Member Author

@kingthorin kingthorin Jul 21, 2025

Choose a reason for hiding this comment

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

Removed

@kingthorin kingthorin force-pushed the split-blog branch 2 times, most recently from bba8e14 to 0b948c5 Compare July 21, 2025 12:55
@thc202
Copy link
Member

thc202 commented Jul 21, 2025

The title PR/commit message should be updated if the new passive scan rule is no longer being included.

@kingthorin kingthorin force-pushed the split-blog branch 4 times, most recently from dce285f to 1326e75 Compare July 22, 2025 11:16
@thc202 thc202 changed the title Blog - Timing Rule Splits/Changes & ZAP is Out of Date Blog - Timing Rule Splits/Changes Jul 22, 2025
@kingthorin kingthorin force-pushed the split-blog branch 2 times, most recently from 3a2427e to 0c62af5 Compare July 22, 2025 11:33
@kingthorin
Copy link
Member Author

Done & done

@thc202 thc202 merged commit 3426545 into zaproxy:main Jul 22, 2025
3 checks passed
@thc202
Copy link
Member

thc202 commented Jul 22, 2025

Thank you!

@kingthorin kingthorin deleted the split-blog branch July 22, 2025 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants