Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cyber Security Cards › Interview Cards

Long-lived IAM access keys committed to GitHub are risky because:

Long-lived IAM access keys committed to GitHub are risky because: A. GitHub blocks all git push B. Stolen keys can call AWS APIs as that principal until rotated/disabled C. Keys improve Argon2 D. Keys replace Security Groups B. Stolen keys can call AWS APIs as that principal until rotated/disabled O

Long-lived IAM access keys committed to GitHub are risky because: A. GitHub blocks all git push B. Stolen keys can call AWS APIs as that principal until rotated/disabled C. Keys improve Argon2 D. Keys replace Security Groups B. Stolen keys can call AWS APIs as that principal until rotated/disabled O
Long-lived IAM access keys committed to GitHub are risky because: · Download PNG
Read card text

What this card says

Options

A. GitHub blocks all git push

B. Stolen keys can call AWS APIs as that principal until rotated/disabled

C. Keys improve Argon2

D. Keys replace Security Groups

Correct answer

B. Stolen keys can call AWS APIs as that principal until rotated/disabled

Why

Once keys are in a public repo, anyone can copy them and call AWS as that account until the keys are rotated or disabled, so they must be killed fast.

Learn more in the lesson: 48.7 CEH-Style Practice Questions – Set B (Modules 11–20)

See all Ravi Sir's Cyber Security Cards