I can agree on the potential headache, but the guidelines that we are having to follow as well as the statement of 'no-action' are somewhat conflicting, stating that generalities are acceptable but specifics are required and many other brain twisters. Slight of hiring another person (or contractor), I am basically left with my own facilities to deal with it. I plan to create the server and enable SNMP for monitoring and then hand over management of the account structure to the Export Compliant Officer. If I do it correctly, the only things that I will need to maintain are the OS patches and the hardware, she will be free to handle the credentials as she chooses. On paper it sounds like a stroke of genius, but good ideas are sometimes the beginning of folly...

 

Michael Haworth

ESSM - PAS Technologies Inc.

D: (816) 556-5157

M: (816) 585-1033

 

From: Nathan Cerny [mailto:[email protected]]
Sent: Thursday, February 25, 2010 1:20 PM
To: Monty J. Harder
Cc: Haworth, Michael A.; KCLUG (E-mail)
Subject: Re: Interesting challenge (for me at least)

 

Any time you have a "shared" set of credentials, it's a bad idea.

I think you're going to end up managing two separate credential stores to make something like this work...

 

On Thu, Feb 25, 2010 at 1:11 PM, Monty J. Harder <[email protected]> wrote:

That domain admin could reset the password for an account with access to the share and gain entry anyway.  A domain admin with a security problem is probably a compliance issue anyway.

On Thu, Feb 25, 2010 at 11:16 AM, Haworth, Michael A. <[email protected]> wrote:

This is most likely pretty elementary, but I wanted to bounce it off of some people that know more than me and can point out any flaws in my very weary logic before I do a concept presentation to my bosses:

 

I have a folder that has to be available on the network (currently Windows with AD), but must be protected from unauthorized access (including access by Domain Admins). Here is what I think a valid solution could be:

 

1.       Build up a CentOS box.

2.       Install and configure SAMBA to allow for sharing to windows computers.

3.       Create a SAMBA share for the required folder (and sort out auto-mount in case of a reboot).

4.       create two accounts - one to allow for Read/Write access to the shared folder and one to allow for Read-only access

5.       Issue the account credentials to the manager of the folder (in this case, out Export Compliance Officer) and then allow it to be that persons problem to manage who knows the credentials.

 

I see this as a low stress, low cost, quick, and above all - easy - way to deal with a potential compliance issue. The reason that we can not simply use Active Directory to restrict access is that one of our Domain Admins is a foreign national - if we were to place a 'deny access' on the folder, he could remove it if he wished - and getting rid of AD or Windows is not an option ATM, but it is still in process.

 

Any help from the list is greatly appreciated,

Michael Haworth

Enterprise Systems Support Manager

PAS Technologies Inc.

D: (816) 556-5157

M: (816) 585-1033

F: (816) 556-5189

 

 

CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.

 

_______________________________________________
KCLUG mailing list
[email protected]
http://kclug.org/mailman/listinfo/kclug



_______________________________________________
KCLUG mailing list
[email protected]
http://kclug.org/mailman/listinfo/kclug




--
Nathan Cerny

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------


CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.