BlueXP is now NetApp Console
Monitor and run hybrid cloud data services
Hi everyone. My name is Dave Tanigawa. I'm a senior storage engineer with NetApp IT and I'm joining you today by way of this video to talk about SnapLock. An annual report by the US Securities and Exchange Commission stated that during fiscal year 22 it filed 760 total enforcement actions and orders for over $6.4 billion in civil penalties, discourgement remedies and pre-judgment interest on behalf of investors regulations such as sox, SEC 17 a-4, hipaa, finra, CFTC, and GDPR obligate organizations to carefully consider how critical data is protected and retained. SnapLock is a licensed high performance compliance solution that allows organizations to use WORM that is right once read many storage to retain files in unmodified form for regulatory and governance purposes. Once the license has been installed, the Snap Lock compliance clock is initiated on each node that hosts a SnapLock aggregate to prevent tampering that might alter the retention period per WORM files. After a SnapLock aggregate and volume are created, the retention time for individual files can be explicitly set, or the retention period can be derived from the default retention time configured for the volume. When we talk about retention period, this refers to the length of time that the file must be retained after it is committed to WORM state. Retention time is the time after which the file no longer needs to be retained. Snap Lock protection is available in two different modes. Snap Lock Enterprise implements best practices for protecting digital assets with WORM storage. Data on a snap lock, enterprise volume cannot be altered or modified. However, data can be deleted prior to the end of the retention period by an administrator using an audited privilege delete procedure. Snap Lock Compliance is the stricter of the two modes. It implements strict data retention for external mandates like SEC 17a-4. Committed volumes cannot be altered or deleted during the retention period, even by an administrator. In addition to regulatory compliance, immutable Snapshot copies and SnapLock can be used to provide a logical air gap backup as part of an overall cyber resiliency strategy. NetApp IT is currently using Snap Lock Enterprise for protecting SOX data and we are using Snap lock compliance to protect critical application data against malicious actions by a rogue actor who has gained admin privileges. In both cases, we vault snapshots to SnapLock volumes where the copies can be committed to WORM preventing deletion. SnapLock is licensed as part of the security and compliance bundle, and a single license entitles you to use Snap lock in either enterprise or compliance mode. There are no restrictions on creation deletion or number of snapshot copies on Snap lock volumes beyond the normal system limits Snap Mirror dump and all other snapshot Copy based technologies are supported with SnapLock volumes. Snap Restore can be used to restore a previous snapshot copy on a SnapLock enterprise file, but it may involve data loss because SnapLock Enterprise assumes that the storage administrator is trusted. However, snap Restore is not supported on SnapLock compliance volumes because this would violate the permanence guarantee and regulatory compliance requirements and the untrusted administrator model of SnapLock compliance data from a SnapLock compliance volume would have to be restored using N D M P copy or Snap Mirror Restore to recover the data on a separate volume in ONTAP nine only like to like Snap Mirror relationships are supported between regular SnapLock enterprise and SnapLock compliance volumes. So SnapLock compliance source volume can only be mirrored to a SnapLock compliance destination. Same with SnapLock Enterprise and regular FlexVol volumes. As with other features in ONTAP, SnapLock functionality continues to improve as new versions of ONTAP become available. SnapLock support for storage efficiency including data compaction, cross volume dedup, and adaptive compression became available beginning with ONTAP 9 91 in ONTAP nine ten one, we introduced the ability for snap lock and non-Snap lock volumes to coexist on the same aggregate Snap Lock is supported with Flex Group volumes, beginning with ONTAP 9 11 1 and in ONTAP 9 12 1, we support snap lock for Snap Vault and Snapshot copy locking requires snap lock licensing and initialization of the compliance clock, but it doesn't use either SnapLock compliance or SnapLock Enterprise snapshots can be locked on any volume either manually or with a retention period configured on the volume snapshot policy locked snapshots cannot be deleted until the retention period is over. I will now demonstrate how SnapLock compliance protects files. Here I have a demo aggregate, which has already been configured for SnapLock compliance, the stricter of the two types of SnapLock. I'm now going to create a snap lock volume on this aggregate with a junction path that the volume will be mounted to. Here we can see that our newly created volume compliance underscore vol has been created with the compliance Snap lock top. Note also that our aggregate contains both Snap lock and non-Snap lock volumes, which can coexist on the same aggregate starting with ONTAP nine ten one. Now I'm going to set the default and minimum retention period for this volume to 30 days. I can run the Vol snapshot, the vol Snap lock show command to see the Snap lock configuration settings for this volume. Now I'm going to create a SIS share so we can access the volume fromour Windows machine in File Explorer. I will now navigate to the compliance underscore vol share, and I'll grab a few files from this marketing folder And copy those to Compliance underscore Vault. Now, the files that exist here have not yet been committed to WORM, so there's nothing that prevents me from deleting a file at this point. One way to commit these files to WORM is to go into the properties and to set the read only attribute. So this file has now been committed to WORM and File Explorer will not let me delete it. I also cannot go back into the file properties to unset the read only attribute. Thank you for watching this video. We hope that the information covered here helps you consider how SnapLock technology can be instrumental in helping your organization with its compliance and cyber resiliency strategies. We look forward to seeing you again next time.
Learn about NetApp SnapLock, a WORM compliance solution for retaining files, and how it can help your organization with its compliance and cyber resiliency.