Verify the lender and loan assignment
Encryption does not prove that the recipient is the correct lender, still assigned to the borrower or using an approved device. Confirm role and assignment through the loan-origination system, minimize the package and send any secret through a separate authenticated channel.
A lender assignment changes during underwriting. Mortgage Operations pauses the handoff, verifies the new lender and approval chain, revokes the old link, prepares the current draft only and records receipt by the newly authorized reviewer.
Run the control in five steps
- 01Verify lender identity, assignment and continuing authorization.
- 02Confirm the exact borrower and draft version to be shared.
- 03Use an approved destination and protected transfer method.
- 04Separate the secret or recovery material from the file channel.
- 05Record receipt, expiry, revocation and final return.
Preserve an accountable decision trail
Keep recipient, assignment source, borrower/loan ID, version, destination, authorization time, transfer and secret channels, receipt, expiry, revocation and exception.
Stop and investigate when
- A forwarded message becomes the authorization record.
- The password travels with the attachment.
- An old lender retains access after reassignment.
State what the control does not prove
Does not replace provider permissions, guaranteed backup, password recovery or enterprise identity management. Validate lender assignment, provider permissions, plaintext copies, retention and recovery separately.
Loan evidence security questions
Does file encryption replace loan-origination platform permissions?
No. Manage identities, roles and provider permissions separately.
Can a shared lender mailbox receive drafts?
Only if policy explicitly authorizes it and individual accountability is preserved.
Sources for this decision
Links support specific control decisions and do not imply endorsement.