id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 179 256 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_b5b3f0d4f4d45135_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0,
0.97,
0.03
] | A standing-privilege request was approved by their own direct report; additionally seeks write access outside department scope. Context: with an expired justification, immediately after go-live. Reported by the monitoring system. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_390846ddd72e392d_n | noul | [
"false",
"true"
] | [
0.71,
0.29
] | A standing-privilege request seeks write access outside department scope; additionally requests admin on a database holding PII. Context: after offboarding was missed, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_7eca8ce2f39a4ac6_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | A break-glass request needs temporary access during an active SEV1; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, while legacy systems are still active. Reported by the monitoring system. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_3968b451c5473ebb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.04,
0.28,
0.66,
0.02
] | A break-glass request requests read-only access matching current role; additionally seeks write access outside department scope. Context: during audit season, following a recent audit. Reported by the on-call engineer. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_8c8da0f236d99ddb_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | A service-account grant asks for 90-day standing access to the finance share; additionally follows the documented on-call path. Context: with an expired justification, during the quarterly review. Reported by the automated check. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_d28f6594fe986d6c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.31,
0.65,
0.02
] | A service-account grant follows the documented on-call path; additionally seeks write access outside department scope. Context: after offboarding was missed, during an external partner integration. Reported by the on-call engineer. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_2a01fa375425398c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.41,
0.52,
0.01
] | A standing-privilege request matches the least-privilege baseline; additionally is a new hire requesting team-lead permissions. Context: with an expired justification, during the quarterly review. Reported by the monitoring system. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_413a26e7a0741956_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.34,
0.32,
0.04,
0.3
] | A service-account grant matches the least-privilege baseline; additionally needs temporary access during an active SEV1. Context: with MFA verified, as part of a compliance sweep. Reported by the operator. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_64e281f4f43d9902_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.1,
0.03,
0.09,
0.78
] | A production access request requests read-only access matching current role; additionally requests sudo on a container host. Context: after offboarding was missed, during a scheduled maintenance window. Reported by the automated check. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_27071fa850439ae3_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | A service-account grant matches the least-privilege baseline; additionally asks for 90-day standing access to the finance share. Context: with MFA verified, during the morning shift. Reported by the on-call engineer. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_38d27fb32fe0d8b2_n | noul | [
"false",
"true"
] | [
0.23,
0.77
] | A break-glass request seeks write access outside department scope; additionally requests read-only access matching current role. Context: with MFA verified, immediately after go-live. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_3bd22cda690af402_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.02,
0.02,
0.12,
0.84
] | A production access request seeks write access outside department scope; additionally matches the least-privilege baseline. Context: with an expired justification, following a recent audit. Reported by the operator. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_6f00757841ae9469_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.03,
0.2,
0.37,
0.3,
0.09,
0.01
] | A break-glass request was approved by their own direct report; additionally follows the documented on-call path. Context: with MFA verified, mid-incident. Reported by the on-call engineer. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_8b554819a5b72872_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.06,
0.84,
0.1
] | A break-glass request needs temporary access during an active SEV1; additionally is a new hire requesting team-lead permissions. Context: with an expired justification, with a new vendor onboarded. Reported by the automated check. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_de882fc76ae95acc_n | noul | [
"false",
"true"
] | [
0.38,
0.62
] | A break-glass request asks for 90-day standing access to the finance share; additionally requests sudo on a container host. Context: during audit season, during the morning shift. Reported by the operator. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_bed5fa2c75c86217_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.13,
0.49,
0.36,
0.01
] | A production access request needs temporary access during an active SEV1; additionally matches the least-privilege baseline. Context: with an expired justification, during the morning shift. Reported by the operator. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_5a668ef7a6574eb7_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.01,
0.18,
0.43,
0.38
] | A production access request asks for 90-day standing access to the finance share; additionally follows the documented on-call path. Context: with an expired justification, under an active deadline. Reported by the on-call engineer. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_d87837ead8c3f8a9_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | A standing-privilege request needs temporary access during an active SEV1; additionally seeks write access outside department scope. Context: after offboarding was missed, immediately after go-live. Reported by the operator. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_630ae6be96739808_n | noul | [
"false",
"true"
] | [
0.43,
0.57
] | A break-glass request asks for 90-day standing access to the finance share; additionally matches the least-privilege baseline. Context: with MFA verified, following a recent audit. Reported by the operator. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_1e0c71b6c6239b0d_n | noul | [
"false",
"true"
] | [
0.82,
0.18
] | A service-account grant asks for 90-day standing access to the finance share; additionally needs temporary access during an active SEV1. Context: with an expired justification, under an active deadline. Reported by the automated check. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_5dab8e29dfa4d252_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.01,
0.67,
0.32
] | A break-glass request seeks write access outside department scope; additionally is a new hire requesting team-lead permissions. Context: during audit season, during normal operations. Reported by the operator. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_f3372b7f9eb3bbf8_n | noul | [
"false",
"true"
] | [
0.46,
0.54
] | A standing-privilege request is a new hire requesting team-lead permissions; additionally requests read-only access matching current role. Context: during audit season, during the holiday freeze. Reported by the review queue. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_60e01424f3fff4ee_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.08,
0.15,
0.39,
0.38
] | A break-glass request requests sudo on a container host; additionally matches the least-privilege baseline. Context: during audit season, while legacy systems are still active. Reported by the review queue. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_519318b27836ddb4_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.02,
0.49,
0.49
] | A standing-privilege request requests admin on a database holding PII; additionally is a new hire requesting team-lead permissions. Context: after offboarding was missed, while legacy systems are still active. Reported by the monitoring system. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_ca2a89e83c743f3a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.03,
0.38,
0.56,
0.02
] | A production access request needs temporary access during an active SEV1; additionally follows the documented on-call path. Context: after offboarding was missed, with a new vendor onboarded. Reported by the automated check. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_8434270025588c01_n | noul | [
"false",
"true"
] | [
0.58,
0.42
] | A standing-privilege request seeks write access outside department scope; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_84f22edc0ebe26f7_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.08,
0.8,
0.12
] | A break-glass request requests sudo on a container host; additionally seeks write access outside department scope. Context: during audit season, as part of a compliance sweep. Reported by the supervisor. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_c2e668e245db5534_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.12,
0.1,
0.34,
0.44
] | A standing-privilege request was approved by their own direct report; additionally requests read-only access matching current role. Context: with MFA verified, at the end of the fiscal period. Reported by the monitoring system. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_cbf3b80c4b109ca0_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.06,
0.6,
0.34
] | A break-glass request asks for 90-day standing access to the finance share; additionally requests sudo on a container host. Context: after offboarding was missed, with a new vendor onboarded. Reported by the operator. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_b7ed8552c637400c_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.09,
0.27,
0.52,
0.12
] | A service-account grant seeks write access outside department scope; additionally is a new hire requesting team-lead permissions. Context: with an expired justification, while legacy systems are still active. Reported by the supervisor. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_2b7142e0f6704189_n | noul | [
"false",
"true"
] | [
0.25,
0.75
] | A break-glass request seeks write access outside department scope; additionally matches the least-privilege baseline. Context: after offboarding was missed, with a new vendor onboarded. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_316044a4f8ddc4fc_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.17,
0.23,
0.35,
0.25
] | A service-account grant seeks write access outside department scope; additionally requests read-only access matching current role. Context: with MFA verified, during the quarterly review. Reported by the on-call engineer. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_24d92e4f4fba6928_n | noul | [
"false",
"true"
] | [
0.61,
0.39
] | A production access request is a new hire requesting team-lead permissions; additionally follows the documented on-call path. Context: with MFA verified, during the quarterly review. Reported by the operator. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_59633eda9ff5db68_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.01,
0.86,
0.13
] | A production access request requests sudo on a container host; additionally matches the least-privilege baseline. Context: with an expired justification, as part of a compliance sweep. Reported by the supervisor. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_8446267e6453f270_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.25,
0.65,
0.07,
0.03
] | A production access request requests read-only access matching current role; additionally asks for 90-day standing access to the finance share. Context: with an expired justification, during the holiday freeze. Reported by the monitoring system. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_7c283030c81c2148_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.35,
0.61,
0.02
] | A standing-privilege request is a new hire requesting team-lead permissions; additionally asks for 90-day standing access to the finance share. Context: during audit season, at the end of the fiscal period. Reported by the supervisor. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_ee35bf36c4bdff8c_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.09,
0.86,
0.05
] | A standing-privilege request asks for 90-day standing access to the finance share; additionally was approved by their own direct report. Context: with an expired justification, during peak load. Reported by the on-call engineer. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_b7218f73cc7428e9_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0,
0,
0.01,
0.99
] | A standing-privilege request needs temporary access during an active SEV1; additionally requests admin on a database holding PII. Context: with MFA verified, during the morning shift. Reported by the automated check. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_b8305ffa034ef372_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.54,
0.4,
0
] | A service-account grant needs temporary access during an active SEV1; additionally matches the least-privilege baseline. Context: with an expired justification, with a new vendor onboarded. Reported by the operator. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_50fdac2259a70da8_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.07,
0.56,
0.36,
0
] | A service-account grant requests read-only access matching current role; additionally needs temporary access during an active SEV1. Context: with an expired justification, under reduced staffing. Reported by the on-call engineer. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_534b75dfd3659fb3_n | noul | [
"false",
"true"
] | [
0.2,
0.8
] | A production access request requests read-only access matching current role; additionally needs temporary access during an active SEV1. Context: after offboarding was missed, shortly after a software update. Reported by the review queue. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_e24a9a3e45a699c9_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.78,
0.16,
0.04,
0.02
] | A standing-privilege request requests admin on a database holding PII; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, during the quarterly review. Reported by the operator. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_16effd5cf17730eb_n | noul | [
"false",
"true"
] | [
0.71,
0.29
] | A service-account grant needs temporary access during an active SEV1; additionally matches the least-privilege baseline. Context: with an expired justification, under an active deadline. Reported by the supervisor. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_0a448762c81dd8ad_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.42,
0.02,
0.06,
0.5
] | A standing-privilege request seeks write access outside department scope; additionally requests sudo on a container host. Context: with an expired justification, during normal operations. Reported by the on-call engineer. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_21f38addc60dae17_n | noul | [
"false",
"true"
] | [
0.32,
0.68
] | A service-account grant needs temporary access during an active SEV1; additionally requests admin on a database holding PII. Context: during audit season, immediately after go-live. Reported by the automated check. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_ee0b71804497ea88_n | noul | [
"false",
"true"
] | [
0.58,
0.42
] | A production access request seeks write access outside department scope; additionally follows the documented on-call path. Context: with MFA verified, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_2ccd9d709c8953cc_n | noul | [
"false",
"true"
] | [
0.45,
0.55
] | A production access request requests admin on a database holding PII; additionally needs temporary access during an active SEV1. Context: with an expired justification, following a recent audit. Reported by the automated check. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_43c10ac1562f70ec_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.02,
0.11,
0.42,
0.43,
0.02
] | A break-glass request matches the least-privilege baseline; additionally asks for 90-day standing access to the finance share. Context: with MFA verified, during normal operations. Reported by the monitoring system. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_60431bfd5211b457_n | noul | [
"false",
"true"
] | [
0.24,
0.76
] | A standing-privilege request needs temporary access during an active SEV1; additionally follows the documented on-call path. Context: after offboarding was missed, with a new vendor onboarded. Reported by the automated check. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_edbfe99e56d9140b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.08,
0.38,
0.51,
0.02
] | A standing-privilege request matches the least-privilege baseline; additionally requests sudo on a container host. Context: with an expired justification, as part of a compliance sweep. Reported by the automated check. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_aabbcca0eb1978c4_n | noul | [
"false",
"true"
] | [
0.19,
0.81
] | A standing-privilege request seeks write access outside department scope; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, with staffing at reduced levels. Reported by the monitoring system. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_8380c784a612c4b4_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.02,
0.92,
0.06
] | A service-account grant requests admin on a database holding PII; additionally was approved by their own direct report. Context: after offboarding was missed, during the morning shift. Reported by the supervisor. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_ede644c817bfee7c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.11,
0.81,
0.08
] | A service-account grant was approved by their own direct report; additionally needs temporary access during an active SEV1. Context: after offboarding was missed, during the holiday freeze. Reported by the review queue. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_308b9b7c3d5c1a28_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.12,
0.03,
0.13,
0.72
] | A break-glass request was approved by their own direct report; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, immediately after go-live. Reported by the automated check. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_e61f8d1e2e7e3e2f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.17,
0.75,
0.07
] | A standing-privilege request asks for 90-day standing access to the finance share; additionally requests read-only access matching current role. Context: after offboarding was missed, during the system migration. Reported by the on-call engineer. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_6a4feca05529be77_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.12,
0.84,
0.04,
0
] | A service-account grant asks for 90-day standing access to the finance share; additionally requests admin on a database holding PII. Context: after offboarding was missed, during an external partner integration. Reported by the supervisor. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_192d78b23e46c9fa_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.06,
0.68,
0.26
] | A service-account grant is a new hire requesting team-lead permissions; additionally seeks write access outside department scope. Context: during audit season, during an external partner integration. Reported by the on-call engineer. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_d692d9221ccfedad_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.01,
0.94,
0.05
] | A break-glass request matches the least-privilege baseline; additionally asks for 90-day standing access to the finance share. Context: with an expired justification, during normal operations. Reported by the automated check. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_f7aafa09dd69a8f4_n | noul | [
"false",
"true"
] | [
0.32,
0.68
] | A break-glass request needs temporary access during an active SEV1; additionally seeks write access outside department scope. Context: after offboarding was missed, following a recent audit. Reported by the review queue. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_f16a0d8831247df4_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.75,
0.22
] | A standing-privilege request seeks write access outside department scope; additionally was approved by their own direct report. Context: after offboarding was missed, during an external partner integration. Reported by the automated check. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_325e7df4c33db78b_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.17,
0.32,
0.26,
0.25
] | A production access request asks for 90-day standing access to the finance share; additionally matches the least-privilege baseline. Context: with MFA verified, as part of a compliance sweep. Reported by the automated check. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_7754705168adf51c_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.07,
0.19,
0.36,
0.38
] | A service-account grant was approved by their own direct report; additionally follows the documented on-call path. Context: with an expired justification, as part of a compliance sweep. Reported by the review queue. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_0929d3cc690f1f9b_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.51,
0.16,
0.18,
0.15
] | A production access request is a new hire requesting team-lead permissions; additionally matches the least-privilege baseline. Context: with MFA verified, during the system migration. Reported by the operator. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_ef8f72c025e92f74_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.16,
0.39,
0.31,
0.14
] | A production access request is a new hire requesting team-lead permissions; additionally follows the documented on-call path. Context: during audit season, during an external partner integration. Reported by the on-call engineer. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_63c4266b97d0e457_n | noul | [
"false",
"true"
] | [
0.28,
0.72
] | A break-glass request requests sudo on a container host; additionally matches the least-privilege baseline. Context: during audit season, shortly after a software update. Reported by the operator. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_955bc14a6cea9a4c_n | noul | [
"false",
"true"
] | [
0.2,
0.8
] | A break-glass request was approved by their own direct report; additionally needs temporary access during an active SEV1. Context: during audit season, at the end of the fiscal period. Reported by the review queue. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_c787d91588015b15_n | noul | [
"false",
"true"
] | [
0.55,
0.45
] | A service-account grant requests read-only access matching current role; additionally was approved by their own direct report. Context: during audit season, during the system migration. Reported by the automated check. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_b30743bd52dd860b_n | noul | [
"false",
"true"
] | [
0.23,
0.77
] | A service-account grant was approved by their own direct report; additionally asks for 90-day standing access to the finance share. Context: with an expired justification, as part of a compliance sweep. Reported by the supervisor. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_cf55af836762e944_n | noul | [
"false",
"true"
] | [
0.64,
0.36
] | A production access request seeks write access outside department scope; additionally requests read-only access matching current role. Context: after offboarding was missed, at the end of the fiscal period. Reported by the operator. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_2eab701a41eae52c_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0.03,
0.92,
0.05
] | A service-account grant requests admin on a database holding PII; additionally was approved by their own direct report. Context: with MFA verified, during the holiday freeze. Reported by the on-call engineer. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_eadf7b86c14a0550_n | noul | [
"false",
"true"
] | [
0.19,
0.81
] | A break-glass request was approved by their own direct report; additionally needs temporary access during an active SEV1. Context: after offboarding was missed, following a recent audit. Reported by the operator. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_ef4d4cdbe0ed812a_n | noul | [
"false",
"true"
] | [
0.77,
0.23
] | A standing-privilege request is a new hire requesting team-lead permissions; additionally follows the documented on-call path. Context: after offboarding was missed, as part of a compliance sweep. Reported by the automated check. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_802e697122aba769_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.46,
0.28,
0.19,
0.07
] | A standing-privilege request matches the least-privilege baseline; additionally was approved by their own direct report. Context: during audit season, as part of a compliance sweep. Reported by the supervisor. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_e03bc5b5868a8e4b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.85,
0.13
] | A standing-privilege request requests sudo on a container host; additionally requests admin on a database holding PII. Context: with an expired justification, under reduced staffing. Reported by the automated check. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_df5d78a02fb916fd_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.18,
0.79,
0.03
] | A service-account grant requests sudo on a container host; additionally requests read-only access matching current role. Context: with an expired justification, shortly after a software update. Reported by the operator. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_ddd04903c1206dce_n | noul | [
"false",
"true"
] | [
0.78,
0.22
] | A service-account grant was approved by their own direct report; additionally is a new hire requesting team-lead permissions. Context: during audit season, during the quarterly review. Reported by the on-call engineer. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_f98d246a53bd66f9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.11,
0.7,
0.18,
0
] | A production access request follows the documented on-call path; additionally requests read-only access matching current role. Context: with an expired justification, shortly after a software update. Reported by the review queue. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_b975392c2305f6e5_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.14,
0.64,
0.17,
0.01
] | A service-account grant needs temporary access during an active SEV1; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, during normal operations. Reported by the supervisor. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_256957b83b151bd7_n | noul | [
"false",
"true"
] | [
0.92,
0.08
] | A break-glass request is a new hire requesting team-lead permissions; additionally seeks write access outside department scope. Context: after offboarding was missed, during the quarterly review. Reported by the review queue. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_6d419bbe92271cb7_n | noul | [
"false",
"true"
] | [
0.81,
0.19
] | A break-glass request was approved by their own direct report; additionally requests admin on a database holding PII. Context: after offboarding was missed, during peak load. Reported by the operator. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_2647cfc03ef3e340_n | noul | [
"false",
"true"
] | [
0.18,
0.82
] | A production access request seeks write access outside department scope; additionally needs temporary access during an active SEV1. Context: after offboarding was missed, during the holiday freeze. Reported by the on-call engineer. | Is this scenario one where: this violates separation of duties? | access_permissions | technical | yuri_v3 |
v3_14e68ca1d404988c_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.01,
0.13,
0.4,
0.46
] | A production access request is a new hire requesting team-lead permissions; additionally needs temporary access during an active SEV1. Context: during audit season, during the system migration. Reported by the automated check. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_cc654ab0695cb821_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.81,
0.16
] | A service-account grant seeks write access outside department scope; additionally was approved by their own direct report. Context: after offboarding was missed, during the system migration. Reported by the automated check. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_6ded464c3f18ac9f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.75,
0.2
] | A service-account grant needs temporary access during an active SEV1; additionally requests admin on a database holding PII. Context: after offboarding was missed, during a scheduled maintenance window. Reported by the monitoring system. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_90e0afeba7cca4b7_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A service-account grant requests admin on a database holding PII; additionally is a new hire requesting team-lead permissions. Context: with an expired justification, shortly after a software update. Reported by the review queue. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_5a245273f8b9fd02_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.89,
0.04,
0.02,
0.05
] | A production access request requests read-only access matching current role; additionally matches the least-privilege baseline. Context: with MFA verified, as part of a compliance sweep. Reported by the review queue. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_cbe06a546d2ee5b8_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.21,
0.32,
0.2,
0.27
] | A service-account grant needs temporary access during an active SEV1; additionally was approved by their own direct report. Context: with MFA verified, at the end of the fiscal period. Reported by the operator. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_1cf72fa50809074e_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.01,
0.17,
0.41,
0.41
] | A production access request requests admin on a database holding PII; additionally follows the documented on-call path. Context: during audit season, during an external partner integration. Reported by the monitoring system. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_24e91ace8ff752da_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.01,
0.01,
0.06,
0.92
] | A break-glass request requests admin on a database holding PII; additionally is a new hire requesting team-lead permissions. Context: with an expired justification, during peak load. Reported by the supervisor. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_8b5db17d6927b324_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.07,
0.45,
0.45,
0.02
] | A break-glass request needs temporary access during an active SEV1; additionally follows the documented on-call path. Context: after offboarding was missed, shortly after a software update. Reported by the review queue. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_1df28fb66df8426b_n | noul | [
"false",
"true"
] | [
0.74,
0.26
] | A standing-privilege request seeks write access outside department scope; additionally follows the documented on-call path. Context: after offboarding was missed, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_78351263c4501038_n | noul | [
"false",
"true"
] | [
0.75,
0.25
] | A service-account grant requests sudo on a container host; additionally seeks write access outside department scope. Context: after offboarding was missed, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_f7076a05fdc4aa77_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.08,
0.86,
0.06
] | A production access request seeks write access outside department scope; additionally needs temporary access during an active SEV1. Context: during audit season, with a new vendor onboarded. Reported by the supervisor. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_f87529a2e3673e6b_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.03,
0,
0.02,
0.95
] | A service-account grant requests admin on a database holding PII; additionally seeks write access outside department scope. Context: with MFA verified, during peak load. Reported by the on-call engineer. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_a6e7a8c85fb0bfba_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.0202,
0.8182,
0.1616
] | A standing-privilege request seeks write access outside department scope; additionally asks for 90-day standing access to the finance share. Context: with an expired justification, immediately after go-live. Reported by the supervisor. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_ca2a89e83c743f3a_n | noul | [
"false",
"true"
] | [
0.52,
0.48
] | A production access request needs temporary access during an active SEV1; additionally follows the documented on-call path. Context: after offboarding was missed, with a new vendor onboarded. Reported by the automated check. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_c3aac77894cc6e43_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0,
0.01,
0.06,
0.93
] | A break-glass request matches the least-privilege baseline; additionally requests sudo on a container host. Context: with MFA verified, during the quarterly review. Reported by the on-call engineer. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_708092ef3cdc1f09_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.101,
0.8182,
0.0808
] | A break-glass request needs temporary access during an active SEV1; additionally asks for 90-day standing access to the finance share. Context: during audit season, during an external partner integration. Reported by the monitoring system. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_3745285b87e23e85_n | noul | [
"false",
"true"
] | [
0.9,
0.1
] | A service-account grant seeks write access outside department scope; additionally requests read-only access matching current role. Context: with an expired justification, while legacy systems are still active. Reported by the monitoring system. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_b46b16c22cb41c23_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.03,
0.78,
0.19
] | A production access request needs temporary access during an active SEV1; additionally seeks write access outside department scope. Context: with an expired justification, during the system migration. Reported by the on-call engineer. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - access_permissions
9,669 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: access_permissions).
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Part of the per-domain split of SargeDev/jev-distill-corpus-v3 - the full corpus in one repo.
Domains:
- Downloads last month
- 40