# FEATURE REQUEST: Auto Create Patch Tuesday Remediation Project

**URL:** <https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586>\
**Category:** InsightVM\
**Tags:** InsightVM, insightvm\_remediation\_projects\_jira\_ticketing\
**Created:** [September 18, 2024, 1:47pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586 "2024-09-18T13:47:59Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lee](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/lee/32/2108_2.png) [@Lee](https://discuss.rapid7.com/u/Lee)\
**Post date:** [September 18, 2024, 1:47pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/1 "2024-09-18T13:47:59Z")

</div>

For customers tracking Microsoft patches/solutions as it related to patching effectiveness each month, it would be incredibly helpful to have an option where InsightVM can auto-create this remediation project on or before patch Tuesday for the upcoming month.

Due to the limitation with remediation data in general not being retained (no data lake) w/o such a project in place before patch Tuesday, customers have to remembers to manually create this remediation project every single month!

---

<div class="post-metadata">

**Author:** ![richard\_davidsson](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/richard_davidsson/32/368_2.png) [@richard\_davidsson](https://discuss.rapid7.com/u/richard_davidsson)\
**Post date:** [September 19, 2024, 12:54pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/2 "2024-09-19T12:54:45Z")

</div>

1+

---

<div class="post-metadata">

**Author:** ![willebille](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/w/f14d63/32.png) [@willebille](https://discuss.rapid7.com/u/willebille)\
**Post date:** [September 19, 2024, 12:58pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/3 "2024-09-19T12:58:39Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![stef](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/stef/32/2671_2.png) [@stef](https://discuss.rapid7.com/u/stef)\
**Post date:** [September 19, 2024, 1:01pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/4 "2024-09-19T13:01:29Z")

</div>

Yes this would be really useful

---

<div class="post-metadata">

**Author:** ![rl2022](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/r/5f8ce5/32.png) [@rl2022](https://discuss.rapid7.com/u/rl2022)\
**Post date:** [September 19, 2024, 1:15pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/5 "2024-09-19T13:15:44Z")

</div>

+500

---

<div class="post-metadata">

**Author:** ![ppersson](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/p/71e660/32.png) [@ppersson](https://discuss.rapid7.com/u/ppersson)\
**Post date:** [September 19, 2024, 1:25pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/6 "2024-09-19T13:25:28Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![wroshon](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/w/c68b51/32.png) [@wroshon](https://discuss.rapid7.com/u/wroshon)\
**Post date:** [September 19, 2024, 6:42pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/7 "2024-09-19T18:42:25Z")

</div>

+100

---

<div class="post-metadata">

**Author:** ![daniel\_gross](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/d/3d9bf3/32.png) [@daniel\_gross](https://discuss.rapid7.com/u/daniel_gross)\
**Post date:** [September 23, 2024, 12:31am UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/8 "2024-09-23T00:31:53Z")

</div>

yes! +1

---

<div class="post-metadata">

**Author:** ![akapaganty1](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/a/48db29/32.png) [@akapaganty1](https://discuss.rapid7.com/u/akapaganty1)\
**Post date:** [September 23, 2024, 11:21am UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/9 "2024-09-23T11:21:15Z")

</div>

Yes +1

---

<div class="post-metadata">

**Author:** ![cstevenson](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/c/9de053/32.png) [@cstevenson](https://discuss.rapid7.com/u/cstevenson)\
**Post date:** [September 23, 2024, 2:35pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/10 "2024-09-23T14:35:13Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![bertrum\_carroll](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/b/3ab097/32.png) [@bertrum\_carroll](https://discuss.rapid7.com/u/bertrum_carroll)\
**Post date:** [September 24, 2024, 1:51pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/11 "2024-09-24T13:51:56Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![avicuna](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/a/df705f/32.png) [@avicuna](https://discuss.rapid7.com/u/avicuna)\
**Post date:** [October 4, 2024, 2:04pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/12 "2024-10-04T14:04:39Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![kgentry](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/k/71c47a/32.png) [@kgentry](https://discuss.rapid7.com/u/kgentry)\
**Post date:** [October 15, 2024, 3:16pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/13 "2024-10-15T15:16:21Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![Lee](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/lee/32/2108_2.png) [@Lee](https://discuss.rapid7.com/u/Lee)\
**Post date:** [October 30, 2024, 1:43pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/14 "2024-10-30T13:43:59Z")

</div>

Related to this, I repeatedly have issues with the Patch Tuesday Remediation Project calculating accurate affected assets.

For example, our Microsoft asset count on the assets page we hover around 4,000 assets month to month. But our Remediation project is inconsistent at reporting affected assets:

April: 896  
May: 530  
June: 3197  
July: 3269  
August: 920  
Sept: 3504  
Oct: 531

My R7 support cases on this have not been able to resolve this over the last few months and one or two occasions, it was due to a verified Insight platform issue. But once the remediation project affected assets count is wrong, we have never been able to recover the correct asset count in the project—resulting in another lost month to report on our vulnerability KPI’s.

---

<div class="post-metadata">

**Author:** ![kl07](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/k/ee59a6/32.png) [@kl07](https://discuss.rapid7.com/u/kl07)\
**Post date:** [November 26, 2024, 8:01pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/16 "2024-11-26T20:01:06Z")

</div>

This is an infuriating topic for us too. We’ve been trying different ways of tracking patch remediation using various combinations of projects, goals, asset grouping, directory syncs, tags, etc… you name it, we’ve tried it… the issue comes back to Rapid7’s presentation of the data (if it’s even there) is hot garbage.

We have also experienced the issue of inconsistent reporting in projects. I could have 100 of the same Microsoft Windows Server 2022 servers in an asset group and one month my project will show 50 servers affected by month X’s patch Tuesday vulnerabilities, yet the next month will show 90 affected. Some t

Part of the issue is that Rapid 7’s own patch Tuesday query (from the Rapid7 published dashboard) isn’t accurate. Using “published date” in the query is what we’ve found limits the results, however even after getting rid of that we still don’t have perfect results.

You would think that if they can present this data as a solution in the projects: ‘2024-11 Cumulative Update for Microsoft Windows Server 2019, version 1809 (KB5046615)’ - that you would be able to query the solution name… or the KB… but, no… you have to have a query with 5 variables that either have to be ALL TRUE (and) … or ANY can be true… (any)… which is one of the worst features of the entire tool… god forbid someone wants to combine an and/or statement. Not ideal.

---

<div class="post-metadata">

**Author:** ![talford](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/t/58956e/32.png) [@talford](https://discuss.rapid7.com/u/talford)\
**Post date:** [November 27, 2024, 10:23am UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/17 "2024-11-27T10:23:49Z")

</div>

> god forbid someone wants to combine an and/or statement

This may or may not help, depending on how you’re doing this, but I’d been using insightVM for years and had exactly the same problem until a few months when I realised you can mix AND\OR together.

In the Query Builder, if you click Switch to Expert you can mix AND\OR together. As example, one of my queries is used to group Windows 10\11 systems with differet hostname prefixes and looks like this:

(asset.name STARTS WITH ‘A1-’ || asset.name STARTS WITH ‘B1-’ || asset.name STARTS WITH ‘C1-’ || asset.name STARTS WITH ‘D1-’ || asset.name STARTS WITH ‘E1-’ || asset.name STARTS WITH ‘F1-’) && asset.os.description CONTAINS ‘Windows 1’

This doesn’t help when creating Asset Groups, which still drives me insane, but it may help in your situation.

---

<div class="post-metadata">

**Author:** ![sgroeneveld](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/s/a8b319/32.png) [@sgroeneveld](https://discuss.rapid7.com/u/sgroeneveld)\
**Post date:** [November 28, 2024, 2:03pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/18 "2024-11-28T14:03:29Z")

</div>

It is unfortunate that the IVM cloud API is so limited.

Wouldn’t it be great to simply monitor xml feeds around patch Tuesday and once you have the CVE’s in question; to create a remediation project.

---

<div class="post-metadata">

**Author:** ![Lee](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/lee/32/2108_2.png) [@Lee](https://discuss.rapid7.com/u/Lee)\
**Post date:** [December 5, 2024, 3:41pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/19 "2024-12-05T15:41:12Z")

</div>

@talford yep, very heavily use Explorer (oh no its also called Query Builder) LOL  
UX consistency please! 😉

I appreciate your responses and would also add for us Patch Tuesday remediation projects have been so inconsistent from an affected assets scope count. The past 4mo the numbers have been all over the place and on average 1,500 assets short when comparing to the Microsoft asset count on the Security Console assets page… :-/

---

<div class="post-metadata">

**Author:** ![tim\_mehrley](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/t/ea5d25/32.png) [@tim\_mehrley](https://discuss.rapid7.com/u/tim_mehrley)\
**Post date:** [December 13, 2024, 10:46pm UTC](https://discuss.rapid7.com/t/feature-request-auto-create-patch-tuesday-remediation-project/42586/20 "2024-12-13T22:46:40Z")

</div>

Yes please.
