So the SCCM environment I've built out for application patching runs two concurrent components: 1. Software Update ADRs that pull from PMPC; 2. Compliance Baselines reporting versions of installed applications. I want to automate every piece I possibly can, and currently the big target is the Compliance Baselines, which require version numbers to be updated by hand each update cycle.
So, what would be nice is for PMPC Publishing Service to generate and then optionally append a simple CSV file for the applications, including metadata like publisher, file version, and applicable CVEs.
Is this feasible?
Justin, here's a really rough idea of what the output might look like. Disregard the bold text formatting for the header. That is just for highlighting the header. CSV obviously doesn't allow text formatting. :-)
Justin, let me throw something together and send it to you.
Casey O�Rourke
Systems Engineer, Infrastructure
121 NW Everett Street, Portland, OR 97209
OFFICE +1 5035485024 | CELL | FAX 503-639-7873
Send me a preview if you want to try an internal preview build.
@Justin Looks good. Adding the column for what action PMPC has taken was a good addition. Just make sure the final version has column headers (obviously). :-)
Something like this look good?
@Justin Nothing more to add in there. Those 5 columns are the ones needed.
@Justin Off the top of my head,
Application Name (just name, no version number),
Update Released/Revised,
Version Number (preferably, when possible, in the four octet format used by Powershell [version] variable casting),
Severity,
CVEs (leave the cell empty if not applicable).
Let me consult with my SecOps person to see if they would like anything else.
@Casey, we are starting to look into this request now. For published updates, could you please let us know what column names you would be interested in having added to the CSV file for published updates and what details from the update would be most helpful? (e.g. update classification, title, severity, URL, etc.)
Thanks, Justin. A couple of us here will be looking forward to that.
I'm hoping we will have the CSV option sometime next month maybe later this month. We haven't started any coding it though, but I don't think it will be a problem.
Thanks, Justin. It didn't seem difficult. Ideally being able to create and then append the same CSV so I can point scripts to a static location. I don't think that would be too difficult?
Also, I've been already looking at the raw RSS feed data to formulate the best method of parsing that data with PowerShell. Doesn't seem too difficult. Just a matter of finding time to do it. :-D
I think we could do a CSV creation. You could maybe use our RSS feed in the meantime? https://patchmypc.com/category/scupcatalogupdates/feed