NSK300 Exam Dumps : Netskope Certified Cloud Security Architect Exam

When multiple DLP profiles are combined into a single Real-time Protection policy, Netskope evaluates the file against all included profiles simultaneously. If the file matches more than one DLP profile, the policy engine applies the most restrictive action defined within the policy and generates a single DLP incident that references all matched profiles. This behavior allows security teams to see comprehensive match information without creating policy sprawl across multiple individual policies. Creating separate policies for each DLP profile would result in multiple independent incidents but would also complicate policy management and potentially cause inconsistent enforcement due to policy ordering. Consolidating profiles into a single policy is the recommended approach when unified action and centralized incident tracking are required.

Netskope’s Quarantine feature allows policy-violating files in SaaS applications to be moved out of their original location into a designated quarantine repository. To configure a Quarantine instance, a Quarantine Instance type must already exist for a supported SaaS application within API-enabled Protection; this instance type defines where quarantined files will be stored within the SaaS environment. A Forensic profile is used for capturing copies of policy-violating files for forensic analysis purposes, not for restoring quarantined files. Encryption is not a mandatory component of the Quarantine profile configuration. A Tombstone file, which serves as a placeholder left in the original file location after quarantine, can be customized by the customer, but Netskope provides a default tombstone, making a customer-supplied one optional.

Netskope’s default steering configuration covers standard HTTP (port 80) and HTTPS (port 443) traffic. When a web application is served on a non-standard port such as 6443, the Netskope Client will not steer it by default. To ensure that traffic on port 6443 is both steered and decrypted, the administrator must enable the “Steer non-standard ports” option in the Steering Configuration and then add the specific domain and port as a non-standard port entry. This configuration instructs the Netskope Client to intercept and forward traffic on that port to the Netskope proxy for inspection. No additional Real-time Protection policy is required solely for enabling steering on this port, as existing applicable policies will be enforced once traffic is properly steered to the platform.