1 / 12

A Proposed SACM Information Model with implications to a SACM Data Model

A Proposed SACM Information Model with implications to a SACM Data Model. Henk Birkholz Nancy Cam-Winget. Proposal. SACM Information Model Defines structure for Data Models guidance Defines guidance on SACM interfaces Can include Data Model Guidance

barks
Download Presentation

A Proposed SACM Information Model with implications to a SACM Data Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Proposed SACM Information Model with implications to a SACM Data Model Henk Birkholz Nancy Cam-Winget

  2. Proposal • SACM Information Model • Defines structure for Data Models guidance • Defines guidance on SACM interfaces • Can include Data Model Guidance • Can include inference to Data Model operations

  3. Proposed Information Model • Intention istoprovidestructureto SACM informationlayout • Structureis a containerthatincludes: • Description ofthe SACM information (metadata) • The contentitself • The Structureallowsfor different Data Models

  4. Information Model Abstract • Highest level SACM statement • Statement Metadata • Globally Unique ID (of Statement) • Data Origin (of Statement) • Data Source (of Content) • Creation Timestamp (of Statement & Content) • Publication Timestamp (of Statement) • Type (of Content) • Statement Content • The Proposed DM • Additional DMs OVAL, SCAP(-AI), DMTF CIM, etc.

  5. Structureofthe DM Content Format providedbythe IM • IM MUST defineelementstoproof inter-operabilityanduse-cases • Beingtooabstractis (probably) bad • BUT someabstractionisneededtoallowagility • Shouldtheelementsbeabstract, e.g. bydefiningsemanticstructuresthatprovideguidanceto DM defintions? • Example: Whatisthe“atomicleaf“ for:Address, IPAddress, IPv6Address • DM decision? Probablyvariesfrom DM to DM

  6. StructureofSACM Content • Statement Content includesoneormore: • Atomic Elements • Grouped Elements • Categorized Elements • Statements canbeCategorizedElements themselves • “recursive“ nestingtofacilitatecorrelation, relay, etc.

  7. Structureofthe DM Content Format providedbythe IM • Grouping (has_a) • Example:NETWORK • IPAddress • SubnetMask • Categorizing (is_a) • Example:Address • IPAddress • IPv6Address

  8. SACM defines a MUST set of elements • A set of Elements will be defined and (most?) identified as MUST to ensure interoperability • Elements have clear semantic understanding to allow DMs to map to SACM’s intent

  9. Element sample • Atomic Elements: • IPv4Address • IPv6Address • Grouped Element: • Endpoint • Endpoint Identifier • <other elements that can identify the Endpoint> • Categorized Element • Software Asset • Software Identifier • Software version • <other elements to identify the asset>

  10. Next steps • Isthereenoughinterest in thisapproachforpresenterstogeneratedrafttextanddetailthestructureandelements?

  11. Comments?

  12. Terms and Mapping of Terms • Onesetof IM Terms forAtomic Elements (Canon) • Varioussetsof DM terms (alreadyexistingandfutureones) • A mapping/dictionaryisrequiredthatshouldbepartofeach DM • Mapping DM Terms with IM Terms • The atomicelementsincluded in the DM contentformatareintentedtobe 100% in syncwiththe IM Terms

More Related