63 replies
by wordworker
Sounds like you need a few policies to get started.
The topmost policy is "all [company] information is [company] property and may not be changed, removed, distributed, or even viewed by any unauthorized person." That lays down the blanket statement that just because you *can* get to some data, that doesn't give you the right to view it, e-mail it, copy it, change it, or destroy it.
Separation of duties based on "need to know." That is, no network account should have access to anything that they don't *need* to have access to. Developers should never be allowed to change anything in production (test and QA environments only). If you use group policies, you can restrict who gets access to say, the SAP applications, by limiting the list of user accounts that can get in.
Disallow logins with service accounts. Some sysadmins sneak in with service accounts so their activity can't be tracked to their user ID.
Data classification policy. Information owners assign a classification for various types of data, such as confidential, sensitive, or public. You can lay related rules or standards like, "Company confidential information must be encrypted before it is sent out of the building," or even "Faxes containing sensitive or confidential information must have a cover sheet with the appropriate legal warning about 'information contained in this transmission.'
Hope this helps!
by kass
by bfilmfan
by wordworker
by james speed
I TOTALLY Agree about not disabling service accounts. The results could be disasterous. If you have a large enterprise, disabling a service account could come back and bite you in the butt so bad you would have a scar. Sometimes these might only run at certain times or dates. A month later next thing you know some critical system isnt working, it takes you hours to figure out whats wrong.
Depending on the size of your organization, you can have an access policy that relates to job function (Role Based Access) and as the other post said "Need to Know". In the Military I posessed a Top Secret clearance, that didnt mean I could eyeball all the spook stuff with impunity. I had to have a valid NEED TO KNOW to access high level stuff and sign a form that I viewed the information- and WHY i viewed it.
Starting off, select the people that need the access and determine if they are indeed trustworthy. Hold everyone with high level access accountable - with each other. Sooner or later if someone is pulling shenagins a teammate will observe it. If you feel you can't trust someone who's job requires "God" level access - either move them to another position or terminate them. If you cant trust them, something is drastically wrong.
Dropping down levels you can start limiting access to other individuals determined by their need. Basically you need to use a "Role Based" access policy from the top down.
Word of caution - if you are taking access away from people who might have it now... do it SLOWLY and methodically. Dont just whack everybody at once and totally take it all away. You will piss off more people than you can imagine and create a very hostile culture. It may be impossible to recover your service scores if that were to happen. Little by little take stuff away - they may (WILL) grumble...but when youre done they have resigned themselves to the fact they cant go EVERYWHERE and ANYWHERE like they use to.
Jim Speed
Network Administrator
Laurens County Healthcare Systems
by croman.pr
In one of the replies, fasthands mention that company information can not be accessed by any unauthorized person.
As an MIS Manager for a small Federal employment and training program in Puerto Rico. I'm responsible to oversee and protect all program clients data files (hardcopy and system files). I only grant access to staff who need to have access to client records and who are authorized to add, modify or delete records.
This is achieved through a "Security Profile" which is nothing more than a document granting access to the appropriate staff. The Security Profile contains a statement notifying the IT staff that access is granted to client records and provide them withof a username and a password to access the data (web application).
This username or password is differente from the username and password usually use to login to the network.
I strongly recommend you enforce data security within your organization by using the tools already came with the many productos available today like ORACLE, SQL and others or thru an ADMIN module in the application. This way you will ensure that non-authorized staff could eventually delete a record or a complete database just by mistaek or intentionally.
by johnjsdc
by phil
1st. Our IT Policy States that all information regardless of format or source, is considered company property, I.E. The "Company" can look at anyones data without any warning or notice,
2nd. No Personal information on Company systems is exempt
3rd. IT Staff are hired partly based on their trustworthyness, Many IT Staffers have access to confidential Company Information, They are forbidden to disclose information they have seen to anybody,
So to recap, IT Staffers have access to all info but above that they are forbidden to use, devulge etc. any information they come accross
However I just noticed that you are a School (by your e-mail) That may change things a little as your policy may have to be more in line with gov agencies and social work, than private corps like us.
by trsnell
by cmc
Please send me a copy of your document...the company i work for is health and in need of something to protect confidential information, specifically employees and clients.
Thankyou
Carol
cmc@rbhs.on.ca
by jpdk
by yosifov
by syao
dear friend,
i would like a copy , please?
Serge
syao@basics.sn
by sphillips84
Would be so kind as to send me a copy of the document.
sphillips@pacificaflac.com
Please can I Have a copy of your Document as well. I work for a small company and we have started to develop company policy's and I feel that this could be very useful to us.
Thanks
James...
I'm thinking we'd all benefit from this policy. Maybe the drafts as well?
llarzelere@oncalltech.net
by blueknight
The data my group deals with involves very sensitive criminal history and inmate information. We are all fingerprinted when hired, and everyone in my group has gone through a background check for felony convictions (I'm the only one with a full law enforcement background clearance). On top of that, the various data owning departments authorize us individually to work on the system by signing an access authorization clearance form which, when completed, goes to our security administrator who then grants the specified access in the system. We also must sign an acknowlegement form that reminds us that unauthorized access to systems and/or data is a crime under penal code secion 502... it gets sent to our personnel file.
This is a bit extreme for most places, but having an authorization form for the "data owners" to sign off might be a real good option for some of you folks.
by harveyck50
by tahlia
Thanks for your kind offer. It will help all of us. Please send mine to tthomas@schoolcraft.edu
Thank you.
by mckenzieg
by roy.balkus
I would very much like a copy of your Policy.
Thanks Roy
roy.balkus@naugsb.com
by cmc
Hello, I work in a Nursing (Healthcare) company with over 100 nurses and would love this form.
Thankyou
Carol
by sganey7
Can you send or post your policy?
sganey@rosettastone.com
by docklas
I don't know if you are tired sending all these copies....
I would appreciate, if you could email one more at docklas@gmail.com
by adilj
Please can you forward me a copy of this poilcy.
adiljan@hotmail.com
I am wondering if you could send me a copy. @ edwardst@selending.com
thanks
by csolloway
by jprivard
Please send a copy to jprivard@bankatcommerce.com
Thank you.
by jbaker
by naser
trsnell,
Very interested discussion, and i need this valuable document, can you please send it to me
ngabaj@gmail.com
I'm in the process of developing a similar policy and would like to see what you developed to meet your organization's requirement.
Thanks.
Jeannine
(Jeannine.Shirley@nasa.gov)
by bletterman
by o.vasquez
by chijmes10
Please send me a copy at this address chijmes10@yahoo.com
Thanks for the effort.
by waynes
I would need a data access policy to clean up mess over here. Could you send me a copy, thanks.
waynes@jdfine.com
by shimes
Hey trsnell,
Could I get a copy of this as well? This would be extremely helpful
for us. shimes@mac.com
Thanks!
scott.
by jounew_a
hi
I would like to get a copy of your policy.
Thank You and Best Regards
Aline Jounewe
by medinats
In this case you should set forth a policy that covers everyone. It is going to be a drawn out process if you are up against management that like to know everything. First things first...is your network shares distributed into departments? If so your implementation is kind of headed in the right direction. Make corresponding groups and make the Department Heads the managers of the access. That is to say when some one needs access to that folder they have to get authorized from that manager. If anyone else gets asked or approves it is still denied till that department head approves the access.
Next is the fun part of putting all the policies into a Board of Education policy. This will allow the policy to effect everything in the school system. If properly explained you should have little resistance on getting it passed best bet there is to explain the security benefits. From there you should make a similar policy for each school or campus under your control and a memo/letter stating that the end users have read and understand it. Now as to what it should say is dependent on how far you want to take it but, you should keep to the Mom rule. If you don't want your Mom to see it then it doesn't belong on the network.
As this applies to your technical staff they should already be well aware of their jobs and should sign it no problem. If you have a rouge, weed him/her out. I am not saying make an example but, make it known that the behavior is not tolerated and ramifications of such things i.e. suspension of privileges, written and filed conferences on his/her work record there at the school, and finally termination. Of course it should never come to the last step but, sometimes we are all a little hard headed.
by bill.doll
My staff and I had a discussion within the department regarding information confidentiality. During the course of their daily activities my staff encounters company, and client data. They understand that anything they see is confidential even within the department and not to be discussed at any time with anyone, unless there is a compelling business/technical requirement.
This goes beyond the data security/confidentiality component of the Companies computer use and security policy all employees sign. I chose not to establish a stricter formal written policy with my staff, instead I provided additional clarification within the context of our access ability within the infrastructure.
by hdalton007
by bill.doll
My staff and I had a discussion within the department regarding information confidentiality. During the course of their daily activities my staff encounters company, and client data. They understand that anything they see is confidential even within the department and not to be discussed at any time with anyone, unless there is a compelling business/technical requirement.
This goes beyond the data security/confidentiality component of the Companies computer use and security policy all employees sign. I chose not to establish a stricter formal written policy with my staff, instead I provided additional clarification within the context of our access ability within the infrastructure.
by rparthas
This is a very valid concern. there are more and more privacy legislation and standards being imposed on organizations. IT staff not only include employees, but in most cases include contractors, sub contracts and outsourcing vendors. When an organization shares a database with them, all the information is shared EVEN if it is only for development or testing purposes. I consider this a major weakness in Internal Controls not to mention bad operational practice.
I have a white paper to share on the subject. I can share that. Email me at rparthas@mhcable.com.
by praetorpal
You have hit the nail on the head; internal controls are often what are lacking. No matter the intentions and how soundly a policy addresses privacy issues, just how does a cub scout promise really protect mission critical data or intelligent property against unscrupulous or disgruntled employees when they see an opportunity to gain financially?
Only core security, such as provided by trusted operating systems and mandatory access controls, can guarantee privacy. With such systems, IT staff can work on systems, but not access files that they do not have security clearance to access. It is definitely the way of the future, but fortunately it is available now.
by todd
If your company is big enough to have a large IT staff were access to information is a problem, your company should have a CIO who would be able to develop, implement and enforce computer use/access policies. The CIO would be the one with ultimate responsibility for all aspects of the IT systems and would be the only one with complete access to everything. Just like we used to say in the old days you can only have one SysOp (system operator).
Also, you would need some system for logging everything everyone accesses with their computers. Without this your wasting your time.
Because:
1) A CIO is usually appointed by the Owner, President, or Board and is trusted to oversee the IT Systems. This is because more and more, in todays times, CIO are being held accountable in the legal arena.
2) Without the ability to monitor ALL accounts, including service accounts, you would have a hard time documenting security lapses and getting convictions when policies are violated. The idea of preventing Service Account logon to an application sounds good upfront, but if a ?service account? exist it usually is needed (if not it shouldn?t exist).
Standard security is to deny access to anything or anyone that does not need access to said information. If you can monitor all activity, you would be able to document unauthorized access and at least which machine the access occured from.
by techierob
What you basically have to do is create a scurity heirachy and appropriate access policy for each security group.
The base policy should be naturally along the lines of "All company data belongs to the company and may not be disclosed, deleted or microwaved etc etc"
In our organisation we have deparments. Our heirachy goes employee -> manager <-> IT Admin <-> CEO.
The reason why IT hangs between the CEO and manager is because any system change must first be discussed with the CEO then the affected manager of the department. If an employee of a department needs appended security changes, I answer to the manager first.
If you are worried about your sysadmins using service accounts to do sneaky things, then the best bet is to hire a new one. If there is no trust with your sysadmin there is no real production.
If you *are* concerned to that extent, enable auditing of all logins to secure locations; if any service accounts are trying to access secure documents, then you know who to blame. Best yet... set all service accounts with uber strong passwords yourself and forget them. Set service accounts with only the security access they need.
As we go up the heirachy, appropriate policies must be set to ensure that even power uses cannot abuse their priveliges. Everyone should be subjected to the same security scruitany as everyone else. If anyone breaks the policy they should be dealt with accordingly
by is
by gsquared
One of the first steps, in my opinion and experience, is a security bond. Basically, have a lawyer draw up a legally binding document that says something along the lines of "I, (your name here), understand that if I disseminate, use, alter or otherwise misappropriate information, business methods, etc., owned by (company name here), I will be legally liable to pay an amount equal to the damages accrued or $10,000, whichever is greater."
Make sure it includes clauses about legal obligations, legal search warrants, etc. You need to be protected if you find that your company is doing something illegal and you "blow the whistle". But other than that, you sign that you will pay the financial penalty if you use any of the confidential data or give it away to others who will use it, either for free or for payment of any type.
The usual use of these is to help prevent/remedy industrial espionage, but it can also be used if you have to maintain the database that payroll data is kept in and you do something stupid with it.
by erishe
You may as well tell your employees -
"You will all be considered incompetent children and be treated as such". That is nothing short of an oppressive leadership ruling with an iron fist, IE: Communism. Your employees are your most valuable resource. You and your HR dept have interviewed and hired them, and they should be treated as professionals until they prove otherwise. Having this type of policy is a huge red flag to your management and your organization. I have written policies for PC usage, Internet usage, SLAs and department procedures. These documents can be tailored to your organizational needs, by protecting company data, users access to sensitive data, company liability and disiplinary actions. You dont need to beat your employees over the head by threatening them with "You will be fined at least $10,000 for any violation." I could go on and on, but I'll leave you with this. If you work for someone like this RUN!
by blcskwr
by blcskwr
by cpr
1) A policy tells you 'what' you want to do. A procedure, guide, standard, etc. tells 'how' to implement that policy. The policy is hardware and software independent. (A policy states that your password must be changed every 30 days - the procedures explain how this is done on all platforms, etc.)
2) Need to identify data owner.
Yes data is owned by the Company. But lets get real! Who can authorize access to Company data? I usually default to the person/department that is empowered to make changes to the application that manages/updates the data.
3) Need to define access levels
A simple 3 or 4 level definition (anyone, company only, restricted, private) solves most issues. The access levels are defined by data 'owners'. Only about 20% of data is 'restricted/private'. A neat technique to help in this area is to use a naming convention (files, folders, etc.)
4) Granting access
Access to 'restriced/private' data must be approved by the data owner. This indicates that the data owner is responsible for the security of his/her data. Just as a judge 'convicts' felons, the security administration 'executes' only convicted felons - they do not worry about guilt or innocence. Also, there must be a data access audit that identifies who has access to which data, and should match against authorized requests.
Too much emphasis is placed on the IT/security groups to protect data. This should be controlled by the stewards of the data and managed by IT/security.
Data loss thru accidental deletes, computer/disk crashes, external intrusions, etc. are the responsibility of the technical support group(s).
by drewtipton
I agree wholeheartedly here when you say that too much emphasis is put onto IT/Security to keep data secure.
Unfortunately, this is what happens. People put data onto a computer, and they suddenly decide that they're no longer responsible for securing that data.
One of my projects many moons ago was the rearchitecture of the payroll system for a mid-sized Silicon Valley software company. I started working with them on requirements, and the Payroll manager consistently said to put on "whatever security I saw fit". I kept trying to get that in concrete terms, but she was never willing to do it. I ended up taking a proposal to my manager (that got implemented) that removed their machines from the "public" internal network, removed internet access, and set a very restrictive password policy.... After that, I never had anyone refuse to answer my questions :)
Ultimately, the people who own the data know who needs access to that data. They can work with the IT and Security people to provide that access, but they are the bottom line!
Dear Sir,
Please send me a free copy. This will help me a lot in providing concrete IT policy in our dept. Thanks a lot
Richard Donato
MIS officer
AHAM Corp.
Quezon City/Philippines
by oretu
Here's the url for the TechRepublic Data Access Policy download:
https://www.techrepublic.com.com/5138-10878-5841908.html
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending