You are viewing limited content. For full access, please sign in.

Question

Question

Permanent redactions without export?

Quick Fields Version 9
Updated January 21, 2015
asked on April 15, 2014

Is there a way to permanently redact SSNs on documents within the Laserfiche repository?

 

I know that you can have Quickfields apply regular Laserfiche redactions, then export the page in question (making the redactions permanent), then reimport the redacted page and replace the original unredacted page. However, that seems like a very inefficient process.

 

Is there some way to locate the SSNs then effectively redact them with a permanent stamp or some similar method?

 

The use case for this is that our clients frequently miss SSNs embedded in existing documents that are being imported or scanned into the repository. It would be quite beneficial to be able to setup some at least semi-automated procedure to redact these "incidental" SSNs.

 

Thanks,

0 0

Answer

SELECTED ANSWER
replied on April 15, 2014

Hey Tim,

 

Honestly Quick Fields would be the easiest way to go about this. You can point the capture source in Quick Fields directly into your repository and it can run the auto redaction on the SSNs that it finds and then merge the documents back into the repository. The only other way to do that aside from Quick Fields would be by using Workflow. But there isn't an activity that will do that out-of-the-box, meaning that you will need to write a custom script. 

0 0

Replies

replied on April 17, 2014 • Show version history

Hi Tim,

 

It sounds like you are also interested in making these redactions permanent, not just automating their application. The easiest (and most secure) way to do so would be to configure your security so that the majority of users do not have rights to see through redactions or edit them. Without rights to see through the redactions that have been applied (either with Quick Fields or manually), the redactions will functionally be permanent for that user. For example, a user without appropriate rights will have no choice but to include the redactions upon export.

1 0
View 3 previous replies
replied on July 23, 2014

Thanks Kelsey,

 

Unfortunately this is more of acompliance issue rather than a practical issue.

 

We have a Standard Administrative Procedure that specifies that SSNs will be removed from files or the files or an exception must be requested from the CISO based on a compelling business need. Even if the exception is granted the files in question must be encrypted, both at rest and in motion.

 

Many of our clients have no compelling business need to have SSNs in their repositories, but some are inadvertently scanned/imported. Rather than deal with the exception/encryption requirement, they would prefer to have a tool that would just remove the SSNs.

0 0
replied on January 20, 2015

Apologies for ressurrecting this old thread, but I've the same requirement. That is, to permanently merge the redacted layer down onto the image once a certain point in the workflow is met.

I assume this is more of an SDK job, but I'm unsure as to how to proceed.

0 0
replied on January 20, 2015 • Show version history

Hi Michael,

EDITED:

First off I will say that as a best practice we recommend keeping your redactions as annotations and using security to restrict access, rather than burning them into the page and removing the original copy of the document.

However, if you need to permanently hide the redacted information and dispose of the original documents you will want to generate new TIFF images to replace your existing ones. 

In order to do this, you have a couple options: 

- After the redactions have been applied (either manually or with Quick Fields), then you'll need to generate pages. The best way would be to set up a Quick Fields session using an account that doesn't have the rights to see through redactions. That Quick Fields session would then reprocess the existing documents in the repository, replacing their existing pages with ones that have the redaction burned into them. Note that this session would need to be separate from any session that is applying redactions.

- To do this without Quick Fields you will need to export the documents in TIFF format with the redactions included, and then re-import them. If you want the documents to retain the same metadata as they had before, you could set up a workflow that, upon import, finds the old document in the repository, replaces the old pages with the new pages that have the redactions burned into them, and then deletes the new document's shell so you are left with only one entry. 

0 0
replied on January 20, 2015

Thanks for coming back to me Kelsey. To be clear, we already have our documents stored as individual TIFF files - not PDF. There are no electronic documents currently.

 

Can you point me in the direction of how to manually generate pages within the client with the above in mind?

 

We have exported all documents to TIFF, which burns the redaction nicely, but ideally we'd like to be able to do this on the repository as well.

 

 

0 0
replied on January 21, 2015

Hi Michael,

My apologies, the previous post was slightly inaccurate. I have updated it with more complete information. Hopefully this helps you!

0 0
replied on January 21, 2015

That's great Kelsey Frost - it gives me enough to work with.

0 0
replied on July 23, 2014

If one of these responses answered your question, please click "This answered my question" to let us know.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...