OVAL script for specific windows OS version

[RC-008]

the build oval definition script works great, but can someone assist a script/direction for creating one for a specific version? i.e. Windows 10, Windows 11, Server 2019, etc. Thank you.

[JohnWilkins69]

Any update on this?

[wmunyan]

In the build_oval_definitions_file script you can use the --platform option to try and filter by specific platforms...

An OVAL definition will have a list of applicable platforms, like this:

      <platform>Microsoft Windows XP</platform>
      <platform>Microsoft Windows Vista</platform>
      <platform>Microsoft Windows 7</platform>
      <platform>Microsoft Windows 8</platform>
      <platform>Microsoft Windows 8.1</platform>
      <platform>Microsoft Windows 10</platform>
      <platform>Microsoft Windows Server 2003</platform>
      <platform>Microsoft Windows Server 2008</platform>
      <platform>Microsoft Windows Server 2008 R2</platform>
      <platform>Microsoft Windows Server 2012</platform>
      <platform>Microsoft Windows Server 2012 R2</platform>

So to build just for Windows 10, you can try --platform "Microsoft Windows 10". It's been a while since I've used/helped write these scripts (and Im no longer at CIS), but I think that's how you'd do it.

PS - I am not sure how responsive anyone will be on these lists anymore, at least from CIS, since anyone who cared about or worked with OVAL has either left CIS or been fired. I doubt CIS' involvement with SCAP/OVAL will last much longer, unless anyone from CIS will comment here stating otherwise.

[RC-008]

Hi Bill, Thank you very much for the response, Yes I have been waiting/hoping since posting the request for a response and completely understood with things that are no longer of interest or supported is going to be tough to get something back. Thanks again! Rasmy From: Bill M ***@***.***> Sent: Wednesday, May 3, 2023 9:47 AM To: CISecurity/OVALRepo ***@***.***> Cc: Rasmy Chiem ***@***.***>; Author ***@***.***> Subject: Re: [CISecurity/OVALRepo] OVAL script for specific windows OS version (Issue #1943) Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. ** Please note that the Sender of this email is from outside CAES ** In the build_oval_definitions_file script you can use the --platform option to try and filter by specific platforms... An OVAL definition will have a list of applicable platforms, like this: <platform>Microsoft Windows XP</platform> <platform>Microsoft Windows Vista</platform> <platform>Microsoft Windows 7</platform> <platform>Microsoft Windows 8</platform> <platform>Microsoft Windows 8.1</platform> <platform>Microsoft Windows 10</platform> <platform>Microsoft Windows Server 2003</platform> <platform>Microsoft Windows Server 2008</platform> <platform>Microsoft Windows Server 2008 R2</platform> <platform>Microsoft Windows Server 2012</platform> <platform>Microsoft Windows Server 2012 R2</platform> So to build just for Windows 10, you can try --platform "Microsoft Windows 10". It's been a while since I've used/helped write these scripts (and Im no longer at CIS), but I think that's how you'd do it. PS - I am not sure how responsive anyone will be on these lists anymore, at least from CIS, since anyone who cared about or worked with OVAL has either left CIS or been fired. I doubt CIS' involvement with SCAP/OVAL will last much longer, unless anyone from CIS will comment here stating otherwise. — Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https:/github.com/CISecurity/OVALRepo/issues/1943*issuecomment-1533060925__;Iw!!BFutyBi9JJrbvoSDvMs!f2joy_Wwj1x3qeHVZx3v-iG4RmqIbZIC0qKA8aYXVmEonVI_OEkMuuEsGZ2GewUhP4wiNaas_V0sfhcbydeDkWkv$>, or unsubscribe<https://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/A67SLUEI7TEE4AP645RPOGTXEJOVJANCNFSM6AAAAAAWUDVXQQ__;!!BFutyBi9JJrbvoSDvMs!f2joy_Wwj1x3qeHVZx3v-iG4RmqIbZIC0qKA8aYXVmEonVI_OEkMuuEsGZ2GewUhP4wiNaas_V0sfhcbyScdxfb4$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>