how to secure/restrict SSN access in Lawson?

Has anyone successfully done any kind of SSN masking at the database level versus using LS Security to secure/restrict SSN? Does it work well with Lawson reports and screens? Query Wizard? Are there any other options out there?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

I too have that question, except that in my case it's another place where an SSN can apear: APVENMAST.TAX_ID (VEN-TAX-ID) Sometimes vendors are small businesses that use the owner's SSN instead of a TIN. We would like to use LS Security to show only the last 4 digits of the TIN. So far this is not figured out yet.

Infor Distribution Management early adopter weekly call-20250102_090236-Meeting Recording.mp4

plancor

We don't have any actual experience since we decided not to implement encryptions during our v9 to v10 upgrade. However, we were told that SQL 2012 Enterprise edition has the ability to encrypt the database and that it is transparent to users and applications. Interestingly, I'm also at a Landmark Admin training class right now, and it was mentioned yesterday that Landmark applications (ie LTM) force encryption for Infor selected fields. In order to access the encrypted data outside of Infor (ie Crystal Reports) you need to use Infor's OLDP driver so that the key is provided.

unknown

Can you give me any more information on "Infor's OLDP driver"? I put in a ticket to ask Infor about this and their reply was " We do not have OLDP driver... But maybe they are referring to OLEDB tool...". Very curious.

unknown

For us, the question is within the Lawson application. There are so many combinations of token security, field security in LS, field security in HR01/HR10, table security, etc. - all trying to restrict SSN. It would be nice if there was a singular way to restrict that access.

unknown

We would also be interested in knowing the right solution as we are in the process of securing the Tax id from all Forms/Batch reports. We are thinking of using Design Studio on the AP10 but not sure of the Reports. Securing from the database end would ideal I think.

unknown

The Tax ID field is best secured from the database access side in LSA. That blanks it out from all screens ... and more importantly ... from "Drill-Around" screens. When I looked at our security setup before our 10x upgrade, I found that securing all screens that show Tax ID from users who don't need it still left a loophole: They could use Selects and Drill-Around to get to where they could see the Tax ID. So, only securing the field is guaranteed to keep it from prying eyes.

Attachment_4233.zip

Maximizing Interactivity in Birst Dashboards.pptx

Derick Safarian

It is possible to use Lawson Security to secure Tax ID from Online Forms and DrillArounds. However, Lawson Security generally cannot remove that field from Batch programs. To secure the field from appearing on an Online form, you could write a "Deny Access" rule on the Tax ID field on the AP10.1 form. To secure the field within the DrillAround feature, you could write a "Deny Access" rule on the APVENMAST table (because the DrillAround feature is based on table access). Lawson Security cannot be used to show only the last 4 digits of the TIN.

Copyright © 2025 Infor. All rights reserved.