What does a secure configuration baseline define?
A secure configuration baseline defines approved settings for a system or device type, including required security features, access rules, logging, and update expectations.
Study 5 Secure Implementation and Configuration with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
What does a secure configuration baseline define?
A secure configuration baseline defines approved settings for a system or device type, including required security features, access rules, logging, and update expectations.
How does minimal functionality strengthen system security?
Install only the components, services, and protocols the system needs; disable or remove unused features and default accounts to reduce its attack surface.
What is a controlled security-update process?
Assess update urgency, test compatibility, deploy the update, and verify installation. Prioritize systems that are exposed or have high impact.
What does least privilege require?
Grant people, services, and applications only the permissions needed for their tasks. Separate routine accounts from administrator accounts.
What protections can mobile device management enforce?
Mobile device management can enforce encryption, screen locks, supported operating-system versions, and approved applications, as well as remote lock or wipe.
How should an organization secure an IoT device?
Change default credentials, disable unused interfaces, restrict network access, and monitor communications. If a device cannot be secured or patched, reduce its exposure or replace it.
What does secure development throughout the SDLC involve?
Build security into the software development life cycle through documented requirements, code review, vulnerability testing, protected development systems, and third-party component management.
What must an order-viewing application check before showing an order?
The application must check whether the user is authorized to access that specific order. Hiding the order identifier in the interface is not an authorization control.
How should applications protect credentials and API keys?
Store credentials, API keys, and certificates in approved secret-management systems rather than embedding them in code or configuration files.
What are the three data states to protect?
Data at rest is stored, data in transit moves between systems, and data in use is being processed.
Why is hashing not a substitute for encryption?
Encryption protects data that must later be recovered in readable form. Hashing can support integrity checking or password verification, but it does not replace encryption for recoverable data.
Why should backup restoration be tested?
Keep backups protected and restrict access to them. Test restoration because a backup that has never been restored may not provide a reliable recovery path.