We had some good ones a few summers ago - I wish I could pretend they were politically motivated in some way but while the catalyst may have been the Police shooting dead a guy*, ultimately it seemed to descend into an excuse to go looting and setting things on fire. Ridiculous situation
@Dan The thing is that even if it starts with a few people genuinely upset about an event (or, more likely, a lot of things during a long time that culminate in an event), they will be joined by a lot of people who are only interested in having the kind of fun that includes destruction of other people's property.
192.168.44.8 is the ip of the server
from console:
telnet 0 22
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.1
telnet 192.168.44.8 22
Trying 192.168.44.8...
Connected to 192.168.44.8.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.9p1 Debian-5ub...
@JennyD Exactly - it spread across the country and people of all colours, beliefs and social classes wound up involving themselves. I'm sure they're rare-ish, but we had stories of white,middle class, law school graduates going to jail after looting shops for TV's and the like
@Dan During the past week or so there were a lot of issues in one of our suburbs. More than half the people arrested weren't even from that area, they'd gone there to join in the "fun", fuelled by media who were actually paying people to burn cars and take pictures of the burning car...
@JennyD No, I have to restart the service... But by default in RHEL, only 10 telnet sessions are allowed from a single source. So if you have a Citrix server full of people connecting to your Linux system via telnet...
So, it turns out that some DNS providers allow you to put CNAMEs in at the root of your domain and then return broken results when anyone queries that domain rather than throwing an error and not allowing the broken configuration in the first place.
@Chopper3 I tried to push for the FusionIO... they are cheap-ish through certain channels... but the RAID situation is a deal-breaker for most clients.
@Cole It told me to run fsck manually so I did. Fixed some missing blocks (?) and it rebooted happily. Of course, since it mounted read-only no logs to be found.
I hope not. I'm going to reboot it a couple times to see if it keeps occuring. Strange since they're 1) new disks, and 2) the OS is basically 2 weeks old.
@Dan Yeah. I gave an hour talk last fall about media retirement. I wish I had had more time. It's hard to talk about records retention as well as retirement for all media types in that length of time.
@Dan It was pretty fun to get to talk about handling both microfiche and SSD in the same presentation, tough.
@Dan AES-256... It could happen.... But it'd still be much easier to social engineer the info out of our clients than to recover it from one of our HDs that you would have to find in the first place... All drives are zero'd too, though I know there's ~20% under-commit.
Our backup media does get shredded (I tend to prefer the word pulverized as the result is pieces about 2x the size of a grain of sand, but point is you wont be reassembling that anytime soon)
This one's a G4. We have another one in service that won't be much longer since it was used for backups ...but we upgraded to using a NAS & external hard drive backup
@Cole we have a dell poweredge for our main server...the HPs were left over from the "old" network. The box I'm re-using used to be a novell netware server
@ewwhite lol, was being snarky. This machine is just crapolla - because its from ebay and has been refurbed. Bits just die regularly. Terrible I/O performance too.
@ChrisS Depending on the algorithm losing the key is considered not entirely unreasonable for data destruction. I would only accept it if the disk is being reused in the same environment. If the disk was leaving out possession I would
@ChrisS I'm working under the assumption that the data is classified as non-public (or whatever the terminology is) under your data classification policy.
If I was working with DoD data I'd secure erase and pulverize... But this is just average person financial data. Most of which could be stolen out of their mailbox of the attacker was local enough to pickup on of our used computers from the recycler.
Our policy only allows for Confidential and Non-Confidential. There's no shades of gray.
@pauska Our recycler has a shredder, so that's what we use. Getting data destruction equipment yourself is too expensive (especially since our recycler only charges us if we need certificates of destruction).
I know a company who wipes harddrives for the military and the norwegian equalent of CIA.. they have to overwrite the disk from start to end more than one time..
Overwriting once gives (each byte) a 1 in a few thousand chance of being read by specialized equipment. Reading meaningful amounts of data from a zero'd drive is practically impossible.
Degaussers also have the auditability problem. Without moving the platters to a new disk you can't check the work. At least with an overwrite or a shred you can do some verification.
@pauska > “Advancing technology has created a situation that has altered previously held best practices regarding magnetic disk type storage media. Basically the change in track density and the related changes in the storage medium have created a situation where the acts of clearing and purging the media have converged.
@pauska > That is, for ATA disk drives manufactured after 2001 (over 15 GB) clearing by overwriting the media once is adequate to protect the media from both keyboard and laboratory attack.” (p. 14, csrc.nist.gov/publications/nistpubs/800-88/…)
@pauska Don't get me wrong, if I was genuinely worried its the route I'd go - I just like people to know that nobody is recovering their once-overwritten drive
@NathanC I put the drives in a box and drop them off at the facility.... After that if I want proof I gotta pay. But they're a non-profit and I know people who work there (it's all on the up and up, at least since they started there a few years ago)
If we had a dead laptop disk we'd likely take it apart and bin it. There's nothing valauble stored on the local disks (well, apart from a copy of Windows and Office)
@DennisKaarsemaker When i get nervous I talk to much about nothing because the silence is deafening and I hate to sit there in absolute silence with the interviewer staring at me intently without speaking because then it makes me feel like I haven't thoroughly answered their question and I keep trying to explain in further detail
there are children being hired in africa to dig up harddrives after they have been buried on those laaaaaaarge computer graveyards that everybody keeps sending their gear to
As I've said before, if you're worried about the NSA reading your hard disk then 1) You've got bigger problems 2) If your fears are justified, they're already watching!
2.5" disks tend to be glass/ceramic. High rotational speeds, so 10k/15k are mote likely to be glass/ceramic. Anything 7200 or lower, and 3.5", is almost definitely not.
Funny "Yahoo" answer to what to do with them... "No. Plug it into your computer and go to disk utility and erase it over 35 times. That is the maximum. 7 times is enough for the DOD so 35 should be good enough for you (probably over kill anyway)"
@Travis Articles like that annoy me. It references the DoD 5220-22M as listing the standards, however it's been a LONG ASS TIME since that document contained any kind of overwrite standards. At one time that document contained sanitization standards, but a long time ago it was updated to state that media needs to be handled according to the Cognizant Security Authority.
@NathanC Right. However, I know a guy that was in a car wreck with an 18-wheeler. He wasn't wearing a seat belt and survived because of it. He will not a wear a seat belt ever again. Contrary to his beliefs, the US Government believes they save lives and have data to prove it...
Generally speaking you just want to ignore NISPOM and look at NIST. It's a lot clearer and more relevant to people not dealing with government data classifications.
Otherwise, if you're talking about auditing then dba, sec.se, or SF would be your best bet depending on exactly how deep you want in which area and what type of expertise you want to attract.
well this is just theory thing in cooperate organizations these duties are largely different, in our place sec people don't have a role in auditing enabling steps
Right. The auditing configuration should be done as a collaborative effort between the security people and the DBAs. The DBAs should probably have access to the audit logs, since it's useful to them, but for liability and investigation issues the storage and collection of the data should be up to the security people.
you can't seriously accept me to login using dba credentials and do their configuration for them, they are all already running sql server for hundred of things why auditing should be so different?
the only way this fits right if we had audit role or separate jd for sec auditor usually windows have a separate group / role for auditors
this doesn't exists; in our case
and even in that retro-respect i don't even expect audit to perform configuration for sql sever they are just to see the changes that are made through logs and other means that nothing has been changed or removed or altered without prior consent or approval
@ChrisS well ideally for log management you need to have proper auditing infrastructure in place ; most people forget this they just worry about syslog 514 traffic its the log sources which are poorly configured and without the right audit controls in place you have little assurance of integrity of the log correlation and management process