unclug AT lists.ibiblio.org
Subject: UNC Linux Users Group
List archive
Re: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8]
- From: "Hill, Jennifer Caitlyn" <caitlyn_hill AT unc.edu>
- To: UNC Linux Users Group <unclug AT lists.ibiblio.org>
- Subject: Re: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8]
- Date: Tue, 23 Apr 2013 13:14:30 +0000
Dell remote tool is called KBox - (you'll also hear it called KACE, since
that's the software suite that runs all the dell sys management tools.)
-----Original Message-----
From: unclug-bounces AT lists.ibiblio.org
[mailto:unclug-bounces AT lists.ibiblio.org] On Behalf Of Palmer, Cristóbal
Sent: Monday, April 22, 2013 10:58 PM
To: UNC Linux Users Group
Subject: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8]
On Apr 19, 2013, at 12:13 PM, "Glassman, Matthew S" <mglassmn AT email.unc.edu>
wrote:
> Could those in the meeting that took better notes than I. List out the
> Security Best Practices rules (11am meeting) and incorporate architecture
> and logging softwares mentioned?
I'm not speaking for ITS or ITS-Security here, so feel free to speak up if
I'm remembering things wrong or am otherwise off base. Also, this is by no
means comprehensive, but since I haven't seen another reply I'll send one.
This mailing list strips slides, but there was a brief slide show and I have
a copy, so ping me off-list if you want that.
This is from memory and not the slides:
= AV =
* AV is not required but is recommended as best practice, especially in
contexts where where Windows machines will have regular access to the host
(eg. a Samba server).
* Where people have an AV solution that meets their needs, no particular
policy or recommendation seeks to push them elsewhere
* For people looking for a solution, SCEP is available for Mac and Linux.
Contact ITS-Security.
= Logging =
(I believe the slides go into more detail here)
* Logging to a separate host is best practice and required in some contexts
* Set up auditd to track things that will be important in incident response
* Several logging tools were mentioned, including rsyslog (the default in
RHEL 6) and Splunk. Others can chime in with what they use.
= Systems Management =
* I brought up puppet. Large development community, puppetforge, ruby-based.
* Others mentioned Chef -- lighter weight and faster, C.
* Another tool was mentioned that's possibly from Dell -- I can't recall.
There was other general discussion that was good, but I also failed to take
detailed notes. Maybe somebody will do that next me, or possibly nudge me to
do so.
Cheers,
--
Cristóbal Palmer
Systems Administrator with Open Systems
University of North Carolina at Chapel Hill
440 W. Franklin St. Chapel Hill, NC 27599-1150
_______________________________________________
unclug mailing list
unclug AT lists.ibiblio.org
We are dedicated to a harassment-free linux education and sharing experience
for everyone. Our anti-harassment policy can be found at:
http://lists.ibiblio.org/mailman/listinfo/unclug
-
Re: [unclug] unclug Digest, Vol 54, Issue 8,
Glassman, Matthew S, 04/19/2013
-
[unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8],
Palmer , Cristóbal, 04/22/2013
-
Re: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8],
Jack Hill, 04/23/2013
- Re: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8], Palmer , Cristóbal, 04/23/2013
- Re: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8], Hill, Jennifer Caitlyn, 04/23/2013
-
Re: [unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8],
Jack Hill, 04/23/2013
-
[unclug] Sparse meeting notes [Was: unclug Digest, Vol 54, Issue 8],
Palmer , Cristóbal, 04/22/2013
Archive powered by MHonArc 2.6.24.