run_94dea702626de9df

jira-triage v1 · jira-triage-k8s · owner ingest:jira-new-ticket (api) · via jira-new-ticket · cloud-engineering

input

{
  "request": "Triage Jira ticket MZCLD-3679: Consider making risk metadata required for new tenants",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3679"
  ],
  "sourceContext": {
    "issue": "MZCLD-3679"
  }
}

summary

MZCLD-3679 is a process-improvement ticket (currently in Backlog, no comments) proposing that risk metadata be required for new tenants during bootstrapping. The reporter bootstrapped a tenant via the bootstrapping skill, deliberately chose risk_level=high per the skill's guidance, but skipped the separate Security Engineering risk assessment survey (used to determine required controls) because the skill described it as non-blocking and never followed up on it in the post-bootstrap report (Phase 8). The gap was only caught later via a security audit, requiring someone else to backfill the risk assessment. The reporter proposes two remediation options: (1) make the risk-assessment metadata a hard requirement at bootstrap time (blocking, deterministic, but complicated by manual review/Google Forms flow and by existing non-conformant tenants needing an allowlist/grandfathering), or (2) improve the skill to more assertively push for survey completion (e.g., auto-open the form, add a Phase 8 verification gate, or repeated reminders) — more ergonomic but less deterministic and reliant on users completing the full skill flow.

findings

[
{
"
d
e
s
c
r
i
p
t
i
o
n
"
:
"
R
o
o
t
c
a
u
s
e
:
t
h
e
s
k
i
l
l
'
s
g
u
i
d
a
n
c
e
e
x
p
l
i
c
i
t
l
y
d
e
c
o
u
p
l
e
d
r
i
s
k
_
l
e
v
e
l
(
c
l
u
s
t
e
r
p
l
a
c
e
m
e
n
t
)
f
r
o
m
t
h
e
S
e
c
u
r
i
t
y
E
n
g
i
n
e
e
r
i
n
g
r
i
s
k
a
s
s
e
s
s
m
e
n
t
(
c
o
m
p
l
i
a
n
c
e
/
c
o
n
t
r
o
l
s
)
,
a
n
d
p
h
r
a
s
e
d
t
h
e
a
s
s
e
s
s
m
e
n
t
a
s
p
a
r
a
l
l
e
l
i
z
a
b
l
e
/
n
o
n
-
b
l
o
c
k
i
n
g
,
w
h
i
c
h
t
h
e
r
e
p
o
r
t
e
r
i
n
t
e
r
p
r
e
t
e
d
a
s
l
o
w
-
p
r
i
o
r
i
t
y
a
n
d
n
e
v
e
r
c
o
m
p
l
e
t
e
d
.
"
,
"
e
v
i
d
e
n
c
e
"
:
[
"
\
"
T
h
e
s
u
r
v
e
y
o
u
t
p
u
t
d
o
e
s
n
o
t
n
e
e
d
t
o
d
r
i
v
e
y
o
u
r
r
i
s
k
_
l
e
v
e
l
c
h
o
i
c
e
h
e
r
e
.
.
.
d
o
n
'
t
b
l
o
c
k
o
n
i
t
.
Y
o
u
c
a
n
a
n
s
w
e
r
h
i
g
h
n
o
w
a
n
d
c
o
m
p
l
e
t
e
t
h
e
s
u
r
v
e
y
s
e
p
a
r
a
t
e
l
y
.
\
"
"
,
"
\
"
I
t
h
i
n
k
I
p
r
o
b
a
b
l
y
i
g
n
o
r
e
d
i
t
b
a
s
e
d
o
n
t
h
e
s
k
i
l
l
'
s
h
e
u
r
i
s
t
i
c
'
t
h
e
o
u
t
p
u
t
o
f
t
h
i
s
s
u
r
v
e
y
d
o
e
s
n
'
t
r
e
a
l
l
y
m
a
t
t
e
r
r
i
g
h
t
n
o
w
'
a
n
d
'
t
h
i
s
c
a
n
b
e
d
o
n
e
l
a
t
e
r
'
.
\
"
"
]
}
,
{
"
d
e
s
c
r
i
p
t
i
o
n
"
:
"
T
h
e
b
o
o
t
s
t
r
a
p
p
i
n
g
s
k
i
l
l
'
s
p
o
s
t
-
b
o
o
t
s
t
r
a
p
r
e
p
o
r
t
(
P
h
a
s
e
8
)
d
o
e
s
n
o
t
c
h
e
c
k
o
r
f
l
a
g
m
i
s
s
i
n
g
r
i
s
k
-
a
s
s
e
s
s
m
e
n
t
m
e
t
a
d
a
t
a
,
s
o
t
h
e
r
e
i
s
n
o
s
a
f
e
t
y
n
e
t
i
f
t
h
e
u
s
e
r
s
k
i
p
s
t
h
e
s
u
r
v
e
y
.
"
,
"
e
v
i
d
e
n
c
e
"
:
"
\
"
I
n
p
a
r
t
i
c
u
l
a
r
,
'
P
h
a
s
e
8
:
P
o
s
t
-
b
o
o
t
s
t
r
a
p
r
e
p
o
r
t
'
m
a
d
e
n
o
r
e
f
e
r
e
n
c
e
t
o
t
h
e
m
i
s
s
i
n
g
s
u
r
v
e
y
m
e
t
a
d
a
t
a
.
I
'
l
l
a
t
t
a
c
h
t
h
a
t
r
e
p
o
r
t
a
s
w
e
l
l
.
\
"
"
}
,
{
"
d
e
s
c
r
i
p
t
i
o
n
"
:
"
T
h
e
g
a
p
w
a
s
o
n
l
y
d
i
s
c
o
v
e
r
e
d
v
i
a
a
n
u
n
r
e
l
a
t
e
d
s
e
c
u
r
i
t
y
a
u
d
i
t
,
m
e
a
n
i
n
g
t
h
e
c
u
r
r
e
n
t
p
r
o
c
e
s
s
r
e
l
i
e
s
o
n
r
e
a
c
t
i
v
e
d
e
t
e
c
t
i
o
n
r
a
t
h
e
r
t
h
a
n
p
r
o
a
c
t
i
v
e
e
n
f
o
r
c
e
m
e
n
t
.
"
,
"
e
v
i
d
e
n
c
e
"
:
"
\
"
t
h
e
c
o
n
s
e
q
u
e
n
c
e
w
a
s
t
h
a
t
s
o
m
e
b
o
d
y
e
l
s
e
h
a
d
t
o
f
i
l
l
o
u
t
t
h
e
r
i
s
k
a
s
s
e
s
s
m
e
n
t
a
f
t
e
r
a
n
a
u
d
i
t
b
y
s
e
c
u
r
i
t
y
d
e
t
e
r
m
i
n
e
d
t
h
e
m
e
t
a
d
a
t
a
w
a
s
m
i
s
s
i
n
g
.
\
"
"
}
,
{
"
d
e
s
c
r
i
p
t
i
o
n
"
:
"
R
e
p
o
r
t
e
r
h
a
s
a
l
r
e
a
d
y
i
d
e
n
t
i
f
i
e
d
t
w
o
c
o
n
c
r
e
t
e
r
e
m
e
d
i
a
t
i
o
n
p
a
t
h
s
w
i
t
h
t
r
a
d
e
o
f
f
s
,
a
n
d
n
o
t
e
s
t
h
e
r
e
i
s
r
e
l
a
t
e
d
/
o
n
g
o
i
n
g
w
o
r
k
a
u
d
i
t
i
n
g
e
x
i
s
t
i
n
g
t
e
n
a
n
t
s
m
i
s
s
i
n
g
t
h
i
s
m
e
t
a
d
a
t
a
,
w
h
i
c
h
i
s
r
e
l
e
v
a
n
t
c
o
n
t
e
x
t
f
o
r
a
n
y
a
l
l
o
w
l
i
s
t
/
g
r
a
n
d
f
a
t
h
e
r
i
n
g
d
e
s
i
g
n
i
f
t
h
e
h
a
r
d
-
r
e
q
u
i
r
e
m
e
n
t
o
p
t
i
o
n
i
s
c
h
o
s
e
n
.
"
,
"
e
v
i
d
e
n
c
e
"
:
"
\
"
W
e
w
o
u
l
d
n
e
e
d
t
o
f
i
g
u
r
e
o
u
t
h
o
w
t
o
d
e
a
l
w
i
t
h
a
l
l
t
h
e
e
x
i
s
t
i
n
g
t
e
n
a
n
t
s
t
h
a
t
d
o
n
'
t
h
a
v
e
m
e
t
a
d
a
t
a
e
.
g
.
b
y
a
l
l
o
w
l
i
s
t
i
n
g
t
e
n
a
n
t
s
t
h
a
t
d
o
n
'
t
h
a
v
e
t
h
e
m
e
t
a
d
a
t
a
.
.
.
A
u
d
i
t
i
n
g
e
x
i
s
t
i
n
g
t
e
n
a
n
t
s
m
i
s
s
i
n
g
m
e
t
a
d
a
t
a
i
s
s
o
m
e
t
h
i
n
g
t
h
a
t
i
s
b
e
i
n
g
a
c
t
i
v
e
l
y
d
e
a
l
t
w
i
t
h
a
n
y
w
a
y
s
e
e
e
.
g
.
\
"
"
}
,
{
"
d
e
s
c
r
i
p
t
i
o
n
"
:
"
T
h
e
t
i
c
k
e
t
r
e
f
e
r
e
n
c
e
s
s
u
p
p
l
e
m
e
n
t
a
r
y
a
r
t
i
f
a
c
t
s
(
C
l
a
u
d
e
t
r
a
n
s
c
r
i
p
t
,
p
o
s
t
-
b
o
o
t
s
t
r
a
p
r
e
p
o
r
t
)
i
n
t
e
n
d
e
d
t
o
b
e
a
t
t
a
c
h
e
d
/
p
u
b
l
i
s
h
e
d
(
i
n
c
l
u
d
i
n
g
a
t
a
n
e
p
h
e
m
e
r
a
l
U
R
L
h
t
t
p
s
:
/
/
w
h
d
-
m
z
c
l
d
-
3
6
7
9
.
q
u
i
c
k
.
m
o
z
i
l
l
a
.
c
l
o
u
d
/
)
,
b
u
t
n
o
a
t
t
a
c
h
m
e
n
t
s
o
r
c
o
m
m
e
n
t
s
c
u
r
r
e
n
t
l
y
e
x
i
s
t
o
n
t
h
e
t
i
c
k
e
t
a
n
d
n
o
C
o
n
f
l
u
e
n
c
e
r
u
n
b
o
o
k
l
i
n
k
w
a
s
p
r
o
v
i
d
e
d
t
o
c
r
o
s
s
-
c
h
e
c
k
.
"
,
"
e
v
i
d
e
n
c
e
"
:
"
\
"
I
h
a
p
p
e
n
t
o
h
a
v
e
t
h
e
C
l
a
u
d
e
t
r
a
n
s
c
r
i
p
t
I
u
s
e
d
f
o
r
t
h
e
s
e
s
s
i
o
n
s
o
I
'
l
l
p
u
b
l
i
s
h
i
t
h
e
r
e
a
n
d
t
o
h
t
t
p
s
:
/
/
w
h
d
-
m
z
c
l
d
-
3
6
7
9
.
q
u
i
c
k
.
m
o
z
i
l
l
a
.
c
l
o
u
d
/
\
"
"
,
"
c
o
m
m
e
n
t
_
c
o
u
n
t
:
0
,
c
o
m
m
e
n
t
s
:
[
]
"
]
}
]

proposed actions

none

tool calls

[
{
"capability": "jira.issue.read",
"args": {
"key": "MZCLD-3679"
},
"result": {
"key": "MZCLD-3679",
"summary": "Consider making risk metadata required for new tenants",
"status": "Backlog",
"description_text": "(or all tenants) I recently bootstrapped a tenant using the bootstrapping skill . Per I missed adding some \u201crequired\u201d metadata. I originally assumed this was because the skills were not updated to require this but upon investigation I found that both the docs and skills included the requirement: were already I happen to have the Claude transcript I used for the session so I\u2019ll publish it here and to https://whd-mzcld-3679.quick.mozilla.cloud/ . But it appears I basically ignored the latter part of the following: Batch 1 of 3 \u2014 part B (choices)\n\nBefore the choice questions, here's important guidance on risk_level:\n\n Strong recommendation: pick high regardless of what the survey says. The risk_level input here and the Security Engineering risk assessment are two separate concerns:\n\n risk_level controls where your tenant runs \u2014 it's combined with your function to pick the target cluster (<function>-<risk_level>, e.g. webservices-high, dataservices-high). The -high clusters are the well-trodden path; landing there avoids edge cases and keeps you on the same footing as most other tenants.\n The Security Engineering risk assessment determines which controls your tenant must align to. That's a compliance output, not a cluster-placement input.\n\n Still complete the assessment \u2014 you need the controls list either way. As of April 2026, you must assess your tenant risk using a simplified and consistent framework defined by the Security Engineering team. The assessment is based on three areas:\n\n Data exposure \u2014 What kind of data is involved?\n Business criticality and visibility \u2014 How important is this to our business?\n Interaction exposure \u2014 Who or what does it talk to?\n\n To determine your risk ratings:\n\n Complete the 10-question assessment form: https://forms.gle/VAJWKxLmqmxdJ1Pk9\n Submit your responses.\n You will receive an automated email with:\n Your tenant's risk ratings\n The required controls your tenant must align to\n\n The survey output does not need to drive your risk_level choice here. For reference, the historical mapping was: rating of 3 or 4 \u2192 high, otherwise \u2192 low. In practice, high is the right answer for nearly all tenants \u2014 only deviate if you have a specific reason and have discussed it with SRE.\n\nIf you haven't completed the assessment yet, I'd encourage doing it in parallel (you'll need the controls list regardless) \u2014 but don't block on it. You can answer high now and complete the survey separately. I just picked \u201chigh\u201d and did not fill out the survey. I think I probably ignored it based on the skill\u2019s heuristic \u201cthe output of this survey doesn\u2019t really matter right now\u201d and \u201cthis can be done later\u201d. The survey was not mentioned ever again. In particular, \u201cPhase 8: Post-bootstrap report\u201d made no reference to the missing survey metadata. I\u2019ll attach that report as well. So I never followed through with adding the risk rating metadata. Since it\u2019s not required metadata I didn\u2019t have to, and the consequence was that somebody else had to fill out the risk assessment after an audit by security determined the metadata was missing. I would like to increase the likelihood that users bootstrapping using the skill actually set the required metadata. I think there are two main options: Make the metadata required This blocks the bootstrapping until results are available. Since IIUC there is a manual security review and some google forms shenanigans this may not be the best idea, but it is also the best way to guarantee the desired outcome. We would need to figure out how to deal with all the existing tenants that don\u2019t have metadata e.g. by allowlisting tenants that don\u2019t have the metadata and only requiring conformance for new tenants. Auditing existing tenants missing metadata is something that is being actively dealt with anyway see e.g. . Make the skill push for survey completion I think the skill could probably be updated to push harder for the survey to be completed, particularly before Phase 8: Post-bootstrap report . It could also e.g. automatically open the form in the user\u2019s browser, or add a required step for verifying the survey is filled out before Phase 8. Changing the skill has the property of being more ergonomic but is less deterministic and relies on the user finishing the bootstrap entirely via the skill. I also find LLMs like to bug you about threads that aren\u2019t complete so if after every step beyond the initial mention it spammed with \u201cstill waiting for survey results\u201d that would probably suffice as well.",
"comment_count": 0,
"comments": []
}
}
]

usage

{
  "model": "claude-sonnet-5",
  "input_tokens": 4560,
  "output_tokens": 2121,
  "estimated_cost_usd": 0.04549500000000001
}

approvals

[]

log

launched k8s job run-run-94dea702626de9df in ns/mzcld-demo-dev image=us-docker.pkg.dev/moz-fx-mzcld-demo-prod/mzcld-demo-prod/agentplat:latest

runner started

live reasoning model=claude-sonnet-5