Describe the Issue
Turn on CSPM for GCP in Azure while CloudGuard is turned down\off
Additional Context
CSPM in Azure is enabled and requires only the AWS & GCP data streams to be turned on to analyze these two other CSP's as well. We can do this while CloudGuard is turned down\off in AWS for cost saving for now and still have CSPM functionality in the meantime
Acceptance Criteria
Research the connection\enablement process\procedure
Review with Warren\Max for the GCP context and review any procedural difficulty
Turn on Azure CSPM for GCP
Test this functionality and troubleshoot
Create further tickets to investigate further for understanding its operation
.
.
.
.
.
.
.
.
.
.
.
Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for
managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)
Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.
Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU
jon-mc-git
commented
1 year ago
Describe the Issue Turn on CSPM for GCP in Azure while CloudGuard is turned down\off
Additional Context
Acceptance Criteria
. . . . . . . . . . .
Extra Template Info
Definition of Ready These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements. Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately. Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint) Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver. Has been sized and estimated by the delivery team. Detailed breakdown of the steps required to complete the story in the additional context Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria A set of pre-defined requirement that need to be met in order to mark the user story as “done”. It should be testable with no room for interpretation It should be either “pass” or “fail” It should be clear enough for business stake holders to understand As part of the user story, it should be written from the user perspective A well written acceptance criteria is great for
Definition of Done These set of conditions are met for work to be considered as complete on an issue. All acceptance criteria(s) have been validated. All the necessary documentation for the issue has been uploaded to Teams. Functionality has been tested when applicable. Functionality has been demonstrated to the relevant stakeholders (where applicable). Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo. Stories accepted by PO and documented for potential sharing with impacted users.