입력 검증

Outcome：Complete the task with 입력 검증 (Input Validation)。 User context：요청을 조작해서 양식을 건너뛸 수도 있어요. 서버는 여전히 알 수 없는 역할 값은 거절해요. Technical concept or control：입력 검증 (Input Validation)。 Why it fits：외부 데이터가 들어오는 모든 경계에서 허용 목록과 스키마를 사용하세요. Do not use it when：클라이언트 측 검사나 알려진 나쁜 문자열 목록만 믿지 마세요. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary)：하나의 공식 표준이 전체 용어를 통제하지 않음. 의미는 팀, 플랫폼 또는 프레임워크마다 달라질 수 있음. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.