A manufacturing company needs to gather logs from specialized controllers and other devices into a unified environment for threat analysis. Some logs contain sensitive data like equipment parameters and login tokens. Which approach best protects these combined records from unauthorized disclosure while allowing analysts to review them together?
Use manual file transfers and merges in a shared folder governed by file permissions
Place logs in a shared repository with open read access for operational convenience
Store logs in separate local storages without encryption for simpler retrieval
Collect logs in a central system with encryption and restricted queries
Protecting logs that are combined in a single location demands stricter controls. Confidential data should be encrypted at rest so that unauthorized access does not reveal sensitive information. Limiting who can query the merged data further reduces exposure risk. Other methods either grant excessive permissions or omit key safeguards, meaning sensitive records could be disclosed to unauthorized parties. Segmenting logs without comprehensive encryption fails to enforce sufficient protection once data is combined. Manual file merges can lead to errors and are prone to mishandling details.
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.
Why is encryption important when collecting logs in a central system?
Open an interactive chat with Bash
What does 'restricted queries' mean in the context of centralized log management?
Open an interactive chat with Bash
Why is manual file transfer not suitable for secure log management?