Downloaded features can change the code present after startup. Cover loading and first use in the protection plan.
Evaluation approach
Verify signing, integrity and dependencies. Sensitive features need their own authorization.
Application example
Recheck the session when a payment module becomes available. Interrupted downloads must not enable partial unsafe operation.
Limits and considerations
A check in the base module may not automatically cover all dynamic features.
What changes at first use?
Download time and execution time may differ. Evaluate session and evidence freshness near the operation. An old startup result does not automatically verify newly available code.
Checks and decisions
- Ask about module coverage
- Test first use
- Exercise interruption
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.