Skip to content

Add Capabilities, Threats and Controls for cloud Monitoring services #811

Open
@rkenefeck

Description

@rkenefeck

Description of Problem:

We need to complete the definition of threats and controls for the Monitoring Services (e.g., Google Cloud Monitoring, Azure Monitor, Amazon CloudWatch )

Potential Solutions:

Add new threats and controls using the guidelines here: https://github.com/finos/common-cloud-controls/tree/main/docs/community-guidelines/content-standards-and-practices

Define the file structure based on services/service-families.yaml which determines monitoring belongs in a subfolder called management and is also missing the services/management/service-categories.yaml definition.

Once this is created, #807 and #808 folders can also live here. This is a different approach to what was proposed in #791

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions