Adding Security Attributes to a Mount Target
Use Zero Trust Packet Routing with a mount target.
If an endpoint has a Zero Trust Packet Routing (ZPR) security attribute, traffic to the endpoint must satisfy ZPR policies and also all NSG and security list rules. For example, if you're already using NSGs and you add a security attribute to an endpoint, all traffic to the endpoint is blocked. From then onward, a ZPR policy must explicitly allow traffic to the endpoint.
Required IAM Policy
To use ZPR with File Storage mount targets, create an IAM policy that grants the File Storage service permission to inspect and use the security attribute namespace required by ZPR.
For example, you can use the following policy:
Allow service <fssoc#prod> to {SECURITY_ATTRIBUTE_NAMESPACE_INSPECT, SECURITY_ATTRIBUTE_NAMESPACE_READ, SECURITY_ATTRIBUTE_NAMESPACE_USE,
ZPR_CONFIGURATION_READ, ZPR_TAG_NAMESPACE_USE} where target.security-attribute-namespace.name = 'applications' The name of the File Storage service user depends on your realm . For realms with realm key numbers of 10 or less, the pattern for the File Storage service user is FssOc<n>Prod, where n is the realm key number. Realms with a realm key number greater than 10 have a service user of fssocprod. For more information about realms, see About Regions and Availability Domains.
Use the
fs mount-target updatecommand and required parameters to add security associations to a mount target:oci fs mount-target update --mount-target-id <mount_target_OCID> --security-attributes securityattributesFor a complete list of parameters and values for CLI commands, see the CLI Command Reference.
Run the UpdateMountTarget operation to add security associations to a mount target.
For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.