OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Secu

 View Only
  • 1.  Layouts in CACAO

    Posted 27 days ago
    All,

    As I work on the layout functionality that was built by Mateusz and Vasileios I would like to flatten out the properties a bit. This is to follow our normal design that we started in STIX that a flatter JSON object is better than nested.  

    1. At the playbook level instead of having canvas_size and then having an object inside of it that contains the height and width, I would just like to do "canvas_height" and "canvas_width".

    2. On the step objects the same sort of thing. Instead of having an intermediary object I would just like to have the x and y coordinates be at the top level. 

    Thoughts? Are you all okay with this?

    Bret



  • 2.  RE: Layouts in CACAO

    Posted 27 days ago
    The rationale behind using sub-objects was that not all playbooks would have layout parameters defined. And it was easier to ignore/add content for layouts in playbooks when its an object with parameters instead of a list of parameters. If you make them flattened list of parameters then it introduces a level of complexity from an understanding / use perspective if you have playbooks with layout vs playbooks without layout.

    If we keep the list of parameters for layout instead of sub-objects then please make sure that it's clear those specific parameters are only relevant if using the layout feature. It is insufficient to just mark them as optional.

    Allan

    On Jun 10, 2025, at 12:27 PM, Bret Jordan via OASIS <Mail@mail.groups.oasis-open.org> wrote:







  • 3.  RE: Layouts in CACAO

    Posted 27 days ago
    Done

    On Tue, Jun 10, 2025 at 4:43 PM Allan Thomson via OASIS <Mail@mail.groups.oasis-open.org> wrote:
    The rationale behind using sub-objects was that not all playbooks would have layout parameters defined. And it was easier to ignore/add content... -posted to the "OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Security" community

    OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Secu

    Post New Message
    Re: Layouts in CACAO
    Reply to Group Reply to Sender via Email
    Jun 10, 2025 6:43 PM
    Allan Thomson
    The rationale behind using sub-objects was that not all playbooks would have layout parameters defined. And it was easier to ignore/add content for layouts in playbooks when its an object with parameters instead of a list of parameters. If you make them flattened list of parameters then it introduces a level of complexity from an understanding / use perspective if you have playbooks with layout vs playbooks without layout.

    If we keep the list of parameters for layout instead of sub-objects then please make sure that it's clear those specific parameters are only relevant if using the layout feature. It is insufficient to just mark them as optional.

    Allan

    On Jun 10, 2025, at 12:27 PM, Bret Jordan via OASIS <Mail@mail.groups.oasis-open.org> wrote:




      Reply to Group via Email   Reply to Sender via Email   View Thread   Recommend   Forward  




     
    You are subscribed to "OASIS Collaborative Automated Course of Action Operations (CACAO) for Cyber Secu" as bret.jordan.sdo@gmail.com. To change your subscriptions, go to My Subscriptions. To unsubscribe from this community discussion, go to Unsubscribe.



    Original Message:
    Sent: 6/10/2025 6:43:00 PM
    From: Allan Thomson
    Subject: RE: Layouts in CACAO

    The rationale behind using sub-objects was that not all playbooks would have layout parameters defined. And it was easier to ignore/add content for layouts in playbooks when its an object with parameters instead of a list of parameters. If you make them flattened list of parameters then it introduces a level of complexity from an understanding / use perspective if you have playbooks with layout vs playbooks without layout.

    If we keep the list of parameters for layout instead of sub-objects then please make sure that it's clear those specific parameters are only relevant if using the layout feature. It is insufficient to just mark them as optional.

    Allan

    On Jun 10, 2025, at 12:27 PM, Bret Jordan via OASIS <Mail@mail.groups.oasis-open.org> wrote: