A software team is updating an application that transforms external data into complex structures for further processing. Logs show that unwanted commands are occasionally triggered after data is loaded. Which control reduces these unauthorized actions?
Postpone data checks until the last step of the process
Apply thorough class-type restrictions during data handling
Expand the set of default libraries that accept remote data
Keep messages in plain text format and rely on local logs
Restricting which classes are loaded from data blocks malicious structures from executing commands. Class-type restrictions verify incoming objects and eliminate harmful data. Postponing checks until the last step misses early risk detection. Expanding default libraries adds more potential entry points for harmful code. Keeping messages in plain text format leaves the application vulnerable if harmful object data is still accepted.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are class-type restrictions in data handling?
Open an interactive chat with Bash
Why is it risky to postpone data checks until the last step?
Open an interactive chat with Bash
Why shouldn't default libraries be expanded to accept more data formats?