Update CISA Track* to Monitor and version by sei-vsarvepalli · Pull Request #841 · CERTCC/SSVC

@sei-vsarvepalli

@sei-vsarvepalli

@ahouseholder

@ahouseholder

Converting to draft to avoid premature merge.

@sei-vsarvepalli

What's different between this and

?

I had been keeping #742 in sync as we merged into main, but holding it as a draft PR so we didn't accidentally merge it until CISA had their changes ready. Also, #742 has more changes in it than just the outcome object in python.

Yeh the #742 diverged too much away from this base. So I just moved to make a smaller PR specific only to this issue - programmatically. It is required for the Decision Tables that I am generating to work properly.

@ahouseholder

@ahouseholder

@sei-vsarvepalli

Hello @j---

Can we get your help in advancing resolution to this? Our hope for September publish release is that this is consistent with CISA and is accurate, especially in the public forums.