Hello - reaching out to our Workfront community to see if any customers have run into challenges in terms of the Workfront environment not meeting requirements for compliance storage (WORM regulations) If so, what solutions have you tried to store da

Hey Natalie! This is a tricky question. One of the things we wanted to ensure when onbiarding WF is WORM compliance. The response from WF was 'sure! we can do that!'. However, the answer was related to WF being able to be customized to create compliance processes. It doesn't seem like it can support the needs for WORM compliance.

Another thing to note is that there is contractual language specific to NOT storing confidential information such as PII in WF.

In reviewing the contract and associated terms/conditions, I did find the following within Workfront’s security terms (https://www.workfront.com/workfront-security) in the Acceptable Use Policy.

This Customer Acceptable Use Policy (“AUP”) describes actions that are prohibited when Customer uses the SaaS Services. Workfront reserves the right to suspend Customers access to the SaaS Services as a result of any violation of this AUP by Customer or any of its personnel.

Customer agrees not to upload or otherwise transmit to or through the SaaS Services any of the following material or other content (“content”):

· content that infringes the intellectual property rights or other rights of third parties, including without limitation trademark rights, copyrights or rights of publicity or privacy;

· content that contains viruses, trojan horses, worms or any other malicious, harmful, or deleterious programs or code;

· content that is libelous or defamatory or otherwise malicious or harmful to any person or entity, or discriminatory based on race, sex, religion, nationality, disability, sexual orientation or age;

· content that promotes or enables any illegal activity; or

¬∑ personal financial information or medical information of any nature or any other non-public personally identifiable information that could be legally considered private or sensitive, including without limitation social security numbers, driver’s license numbers, birth dates, personal bank account numbers, passport or visa numbers, passwords, and credit card numbers.

All that being said - our team is looking to explore Box.com but we haven't gotten that far yet.

I think that's a long way of giving you way too much information but hopefully that helps!

We struggle with this as well. Bookmarked so I can follow other responses. Thank you for posting this topic, Natalie.

We had a good convo about this in the @Financial Services‚ group and a member of our product team suggested the following on this thread.

Brent said: "Workfront by itself will not meet the FINRA requirements from a WORM archival standpoint. However, with a Fusion integration you can definitely connect to a WORM compliant solution so you can satisfy this requirement. When at Charles Schwab, WF was used as the source of truth of content initiation as well as approvals and then a summary file was generated to house the approved assets, date and time stamp, approver, any comments associated with the assets and the products being featured inside of the piece of content. This was then archived inside of the official archival system of record which was integrated with Workfront. If you would like to speak more about this, please feel free to shoot me a note at rudewick@adobe.com and I can help you build something that will work with the regulators."