Which mechanism helps prevent unauthorized access to address export functionality?

Which mechanism helps prevent unauthorized access to address export functionality?

• A. Access controls and secure export procedures
• B. Allow all employees to export
• C. Disable logging for exports
• D. Hide export feature behind internal API

Answer: (A)

Controlling who can export data and how the export is handled is the core idea. Access controls enforce who is allowed to initiate an export, what data they’re permitted to export, and under which conditions. When you pair that with secure export procedures—strong authentication and authorization, validation of the request, least-privilege access, audit logging, and encryption for data in transit and at rest—you create a robust barrier against unauthorized exports. This kind of defense makes it clear who can export, what they can export, and provides traceability if something goes wrong. Why the other options aren’t as solid: allowing all employees to export breaks the security boundary and invites risk. disabling logging eliminates accountability and makes it impossible to detect misuse. hiding the feature behind an internal API only helps if that API is itself tightly secured; obscurity isn’t a reliable defense on its own and can give a false sense of security.

Controlling who can export data and how the export is handled is the core idea. Access controls enforce who is allowed to initiate an export, what data they’re permitted to export, and under which conditions. When you pair that with secure export procedures—strong authentication and authorization, validation of the request, least-privilege access, audit logging, and encryption for data in transit and at rest—you create a robust barrier against unauthorized exports. This kind of defense makes it clear who can export, what they can export, and provides traceability if something goes wrong.

Why the other options aren’t as solid: allowing all employees to export breaks the security boundary and invites risk. disabling logging eliminates accountability and makes it impossible to detect misuse. hiding the feature behind an internal API only helps if that API is itself tightly secured; obscurity isn’t a reliable defense on its own and can give a false sense of security.