What configuration control can block sensitive information from being stored in a SaaS solution?

The ability to block sensitive information from being stored in a Software as a Service (SaaS) solution is best achieved through content filtering. This approach involves inspecting data and applying rules to determine whether it should be allowed or denied based on its content. For instance, content filtering can help prevent the storage of sensitive data such as personally identifiable information (PII) or confidential business information within the SaaS application by analyzing the content before it is sent and applying policy-based controls.

By utilizing content filtering, organizations can ensure that sensitive data does not inadvertently get uploaded to SaaS platforms, thereby protecting it from unauthorized access or data breaches. This is crucial for maintaining compliance with data protection regulations and safeguarding organizational data.

The other options, while valuable in their own right for securing a network or data, are not specifically designed to prevent sensitive information from being uploaded to a SaaS solution. File-level encryption protects data at rest or in transit but does not prevent sensitive data from being sent in the first place. Network ACLs control access to network resources rather than data-specific policies, and an Intrusion Prevention System (IPS) focuses on detecting and preventing attacks within the network but won't specifically block sensitive data from being stored in a SaaS application.