Verifying the Requester and the Legal Process
Readiness training. LEA.Training does not grant any official certificate, licence or authority.
A request has arrived, and it has a row in the request log (unit P1, Receiving and Logging Requests; Publishing Your Rules). It looks official. It may be genuine. It may be a forgery, sent by someone who wants a user's home address.
Answer two questions before you look at any data. Who is asking? What legal paper do they hold?
Focus: verify the person, then the paper. Urgency is never a reason to skip either check.
Learning objectives
- Check a requester's identity by domain, call-back and service details.
- Say what a portal account proves, and what it does not.
- Handle a request from a foreign authority, or one that arrives through another authority.
- Check a legal document: right type, right authority, signed, in date.
- Recognise the warning signs of a forged request, above all a forged emergency request.
- Use a verification checklist and record the result.
This lesson opens when you enrol
US$— · price for the Global edition is not set yet
Already bought it? Sign in to open it in your classroom.
Video coming soon. The lesson text covers everything you need.
Learning Check
A short, untimed check for this lesson. It is not graded and does not count toward the final assessment. The check runs on the server: questions are sent one attempt at a time and answers are never sent to your browser before you submit.
An offline PDF of this lesson will be available here for enrolled learners.