| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10
Comments:
<0> I can backup history file in real time.
<0> but like then they can unset histfile and maybe rm the history file
<0> I need to make it so they can't :)
<1> hrm, maybe trusted solaris?
<0> hmmm
<0> thats a biiatch to setup
<0> but yes I thought about it :)
<0> I can't replace existing OS with that... it will stuff many things.
<0> the hard thing is... when a user "su" and as root they remove files..
<0> harder to log.
<0> But I did setup some administrative task logging.. you have to piece it together.
<1> nothing is foolproof
<0> using time stamps I suppose :(
<0> true
<1> we use sudo+a logging rootshell
<0> ahh
<0> how do you do that anyway?
<1> but it doesn't stop anyone with root from connecting to the console, typing the root p***word and doing whatever
<0> just a flag you use with sudo?
<1> someone hacked bash
<0> **** all admins have console access
<0> hehe
<1> to add sudo-like logging to every command
<0> not everyone here uses bash
<1> yea
<1> well
<1> if they want a rootshell they do!
<0> ahh I see
<0> lol
<0> I can't restrict that ;)
<0> admins use ksh/bash
<0> ill google it there must be some methods:)
<1> gotta have policies man
<0> yeh
<0> we have "security polocies"
<0> just we don't probably use them :)
<0> hehe
<0> Administration Based on Solaris Management Console 3.0 FCS Framework and NIS+
<0> hmm
<0> do many companies use trusted solaris?
<0> would be nice to gain skills in configuring if so.
<1> i've never seen it as a req
<0> Trusted Roles
<0>
<0> There are no superuser accounts with Trusted Solaris 8 software; systems administrators are as accountable for their actions as users.
<0> woot
<0> policies I meant I can't spell
<2> OMG YOU RULE
<1> LOLOMGWTFBBQAIDS
<0> normal unix is C2 if auditing is turned on
<0> apaprently trusted unix is "B" grade
<0> windows is D ;)
<3> who gives a ****?
<2> phaedrus, BSM does
<2> obviously he cares about security, since he chose a security acronym as his nickname.
<3> oh!
<1> BigStinkyManhole
<3> and here I was thinking the S was a typo
<1> heh
<1> hows the kid phae?
<0> trusted solaris is used by military bigbambu
<0> would be sweet wokring for DoD
<1> uhm
<1> no it wouldnt.
<0> heh
<0> challenging
<2> *BSM* thanks ;) [23:14:35]
<2> *BSM* that guys grumpy. [23:14:43]
<2> *BSM* interesting spoof. [23:14:53]
<0> hehe
<2> bambu, are you grumpy?
<0> not him
<0> Phaedrus is grumpy.
<0> or just doesn't like my babble.
<3> bb he's doing very well
<3> yeah, I have no reason to be grumpy, you're simply annoying
<0> hehe
<2> well, it does appear as if you are chatting to see yourself chat.
<0> Im kinda ranting on.. and hoping someone will teach me.
<0> maybe you will advice against my ideas and I will learn why:)
<2> maybe not
<0> so far it's been quite good help here
<0> form bigbambu
<0> I should start paying him.
<2> he prefers to be paid in rimjobs
<0> I heard he prefers milshakes.
<4> i'm grumpy
<4> who wants a kicking?
<3> not me
<2> grumpchick
<3> hey I tried to contribute to your happiness today
<4> you did :D
<3> if it didn't work, it's not my fault!
<4> haha it totally worked
<5> pft
<4> same to you
<3> I blame niki
<3> for not looking cute enough
<3> he should try harder
<5> yeah
<5> or something
<0> haha
<0> The decision about whether or not to include the other "file" event cl***es to track creating, deleting, reading, and modifying files was probably the most contentious aspect of our auditing discussions within CIS.? Sun[2] recommends avoiding these audit cl***es in order to reduce the size of the audit trail.? On the other hand the DoD guidelines[1] require tracking at least failure for these cl***es (actually the specific recommendation is
<0> "fw,-fc,-fd,-fr").
<0> hmm tough one.
<0> does anyone else use those guidlines?
<0> DoD recommended ones.
<3> again, this would ***ume that anyone here gives two ****s about security
<1> heh
<0> ofcourse you do
<0> you're all most likely sys admins?
<1> we have a seperate dept. that worries about security
<0> I am ***uming Phaedrus doesn't work with a bank ;)
<1> all we do is keep servers serving
<0> ahh
<0> monitor events?
<1> NOPE
<0> what then?
<1> monitoring dept does that
<0> hardware?
<0> lol
<1> we just keep the servers serving
<1> now ask me about the network
<0> what exactly does that require?
<1> so i can say
<1> THE ROUTING TEAM DOES THAT
<0> I don't understand your role.
<0> what does that require form you.
<0> to make sure there powered on?
<1> build/configure/maintain 1000+ production servers
<1> along with various bits of storage
<0> well maintain can be on many levels
<1> but we dont monitor the servers, or worry about security
<1> other do that.
<1> others
<0> fair enough
<0> "maintain" as in sys admin tasks... users and crap?
<1> users/procs
<0> add/remove.. scripting..
<1> etc.
<0> is there a "backup team
<1> nope
<1> we do that
<0> oh
<0> how cool
<0> ;)
<1> but we dont control database backups
<1> DBAs do that.
<1> all we do is provide tapes etc.
<0> yeh fair enough same here
<0> what about system backups?
Return to
#solaris
or
Go to some related
logs:
army's on extacy
diana 7ayak
EXT:RDP password
#computers
#flash
eerie channels 1825
#beginner
#dsl
#openbsd
#nhl
|
|