Bài kiểm tra có liên kết hướng dẫn · Trung bình Cấp độ
Bài kiểm tra phát hiện chiếm đoạt tài khoản
Phát hiện việc chiếm đoạt tài khoản bằng cách sử dụng chuỗi sự kiện và kiểm soát theo lớp, đồng thời cân bằng giữa việc ngăn chặn gian lận, khóa sai, khôi phục an toàn và quyền riêng tư.
Câu hỏi 1 của 8
Which event constitutes an account takeover?
Xem trước mọi câu hỏi8 câu hỏi
Câu trả lời và giải thích xuất hiện khi bạn làm bài kiểm tra.
- Which event constitutes an account takeover?
- A legitimate owner changes their own password through verified recovery
- A merchant reverses a disputed payment
- Unauthorized access to an existing account followed by actions as its user
- An attacker guesses a password but never gains account access
- What does credential stuffing involve?
- Guessing many possible passwords for one account
- Trying previously exposed credentials on another service
- Trying one common password across many accounts
- Resetting a password through the account’s verified recovery flow
- Why can a sequence of account events be more informative than one login signal?
- One device change always proves fraud
- Event ordering is never useful
- Transactions cannot be connected to logins
- Several linked actions can form a suspicious progression
- Which response is an example of step-up security?
- Requesting an additional verification for a high-risk action
- Allowing every transaction without checks
- Revoking every customer session after each login
- Permanently deleting the account
- Why must account-recovery flows be designed carefully?
- Recovery has no connection to account security
- A model can always identify the true owner
- Attackers may abuse recovery while legitimate users need accessible access restoration
- Account recovery should be impossible
- Which metric helps reveal harm from overly strict detection?
- Only model training loss
- Legitimate account lockouts and recovery time
- The share of sessions using different device types
- Password length among signed-in users
- What should customer-support teams never request through an untrusted channel?
- A case reference number
- A preferred contact time
- A non-sensitive device model
- A password or one-time authentication code
- Why avoid exposing detection thresholds and rules?
- Attackers could tune behavior to evade the controls
- The rules are public by default
- It prevents legitimate users from signing in
- It changes the model labels