SKH
Well Known Member
Hi,
I'll try and keep it brief (may be a challenge ) -
In short, security has been more or less overlooked at the site I work at (there's a first!). Yes - there is some basic security defined but a lot of work to be done.
It has been decided that as a starting point or a 'quick win', we need to secure the users to the data they can see / retrieve from the system (using company).
So, I've been having a play with the new Business Unit Security in our release of E1 (8.11). This is fine but requires us to identify a list of transaction tables that we want to secure. This is quite a large task in itself and so the question was raised 'Why don't we use Row Security against *ALL tables for defined Roles?'. Obviously, this will have a performance hit but we are currently testing this on our Dev System and on the whole it does the job.
I have some Apps people currently testing and some errors are popping up e.g. Batch Post fails with security configured at company level (an issue known by Oracle but with no resolution).
Just wanted to get some ideas/thoughts on this whole area. Anyone going through/been through a similar exercise? Is what we are testing the 'proper' way of going about this task?
I have an idea of how security should have been tackled, having worked previously for a company that spent 18 months or so planning/implementing security with a dedicated Security Officer/team. But obviously at my current site, it's fairly late in the day for this . So I really am after how we can achieve the 'quick win' or 'can we?' for the moment.
Thanks / Best Regards,
Sanjeev
ps. I'm a CNC bod
I'll try and keep it brief (may be a challenge ) -
In short, security has been more or less overlooked at the site I work at (there's a first!). Yes - there is some basic security defined but a lot of work to be done.
It has been decided that as a starting point or a 'quick win', we need to secure the users to the data they can see / retrieve from the system (using company).
So, I've been having a play with the new Business Unit Security in our release of E1 (8.11). This is fine but requires us to identify a list of transaction tables that we want to secure. This is quite a large task in itself and so the question was raised 'Why don't we use Row Security against *ALL tables for defined Roles?'. Obviously, this will have a performance hit but we are currently testing this on our Dev System and on the whole it does the job.
I have some Apps people currently testing and some errors are popping up e.g. Batch Post fails with security configured at company level (an issue known by Oracle but with no resolution).
Just wanted to get some ideas/thoughts on this whole area. Anyone going through/been through a similar exercise? Is what we are testing the 'proper' way of going about this task?
I have an idea of how security should have been tackled, having worked previously for a company that spent 18 months or so planning/implementing security with a dedicated Security Officer/team. But obviously at my current site, it's fairly late in the day for this . So I really am after how we can achieve the 'quick win' or 'can we?' for the moment.
Thanks / Best Regards,
Sanjeev
ps. I'm a CNC bod