Data replication for governance
Just from a low tech management perspective, to get an idea for data governance more than anything, if say you have a payroll appliction storing sensitive data, can you give me some examples where the database's data could potentially be replicated in locations other than the main application database. I have some idea of replication whereby for high availability the data could be mirrored across several servers. I was just after a list of whereby data for an application may be cloned.
My concerns and the main driver for this question are that if data protection is an area of concern, and auditors just look at the main database for the application, if the data is also replciated in X, y, z location a vulnerability in x, y z location could expose the data to unauthorised access...
These are MS-SQL databases on VMware hosts, Windows 2008 guests...
My concerns and the main driver for this question are that if data protection is an area of concern, and auditors just look at the main database for the application, if the data is also replciated in X, y, z location a vulnerability in x, y z location could expose the data to unauthorised access...
These are MS-SQL databases on VMware hosts, Windows 2008 guests...
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
<can you give me some examples where the database's data could potentially be replicated in locations other than the main application database?>
please clarify your question
please clarify your question
I was thinking along the lines of database backups, database mirroring etc.
I.e. a novice may think that an applications data is only in 1 database on one server in the network. But I suspect in high availability environments thats rarely the case. I was trying to get a quick overview of real life examples where data would be replicated in numerous locations therefore security controls need to consider each of these....
I.e. a novice may think that an applications data is only in 1 database on one server in the network. But I suspect in high availability environments thats rarely the case. I was trying to get a quick overview of real life examples where data would be replicated in numerous locations therefore security controls need to consider each of these....
less sensitive data replicated to different servers- less chance\risk to compromise this data...
for HADR-- you need to check with you firm regulations\business requirements\budget..
start with cluster server\ check mirroring and in any case have a good
\fresh db backup..\have regular db maintenances\
--
but as an example: it is good to have some "test" server(s) with the same security as prod (for sensitive data) to test new application releases prior deployment in prod (MO\Qa servers\environments)..
and due to avoid any headache-- scrub all sensitive data o test servers before letting testers\qa to play with a new release
for HADR-- you need to check with you firm regulations\business requirements\budget..
start with cluster server\ check mirroring and in any case have a good
\fresh db backup..\have regular db maintenances\
--
but as an example: it is good to have some "test" server(s) with the same security as prod (for sensitive data) to test new application releases prior deployment in prod (MO\Qa servers\environments)..
and due to avoid any headache-- scrub all sensitive data o test servers before letting testers\qa to play with a new release
Premium Content
You need an Expert Office subscription to comment.Start Free Trial