The only reason y2k didn't "happen" was because corps spent a ton of money and time fixing code and replacing computers. It wasn't just ignored and passed as a non-event. Everyone I know in IT at the time worked on various mitigation upgrades...from recoding mainframes to replacing desktops of entire companies.
Indeed, that really wasn't random either. My guess is the father was getting ready to legally take the kids away, so she flipped out and decided their better of dead than without her.
"I, Robot" is a collection of short stories. As "Golden Age" scifi it's top-of-the-line, but it's pretty outdated so any one story from it would make a pretty horrible movie. Smith's movie actually incorporates several themes and ideas from the original book. Personally, I thought the movie was quite interesting, especially the idea of "emergent behavior". We're just now using the idea in swarm programing of bots, letting them figure out their own best patterns of moving around together.
Unless you specifically WANT to get out of jury duty, then I suggest you saying something like "I believe in jury nullification and look forward to educating my fellow jury members if chosen for a case."
This comment should be +5, not 0. A close friend of mine works in ITSEC at a major research hospital. GE is one of his major headaches; their patch cycle doesn't come close to keeping the equipment secure. You can't just install any OS you want on them; nor can you just patch them at will. All of this is FDA regulated. Change anything outside of the manufacturer's allowance and you break the certification...which breaks the "warranty", support contract, and the whole insurance liability chain. A partial solution is vlans/separate physical networks...but only hospitals with $$$ can afford this. He's lucky that his workplace is very well funded (they even paid for his CISSP certs) and he has a whole team dedicated to security. Many hospitals just do the bare "Required" parts of HIPAA, which is aimed at an office manager's simple checklist.
Their using something called MyVCM to "to ensure we operate a robust information security and privacy program", whatever that actually means. I found this, which at least mentions " HIPAA, NIST, FedRAMP, COBIT, COPPA, ISO/IEC, and PCI DSS". Not sure just what particular NIST their referring to, but any company that actually pays attention to the 800 series and doesn't just go by the scant HIPAA security "regulations" is at least looking in the right direction. All of this is straight off the HIPAA Security ruling. Caremonkey won some award. Their based out of Australia.
I wouldn't use them. Because CodeMonkey comes from Australia, and, as everyone knows, Australia is entirely peopled with criminals. So you can clearly not choose the cloud-based provider in front of you.
Few people have the patients and planning capabilities to pull off what McVeigh did. It's relatively easy to go buy a gun and shoot people; making a moving truck full of home-made explosives takes time, effort, and real planning. It takes awhile to produce 5,000 pounds of explosives.
LOL, indeed. Your story reminds me of when I finally got to go into the "secure bunker" area of the old SABRE cold-war underground data center. Some ancient SCO box, making a horrible whining noise...a stack of other boxes of the same model next to it, we had already scavenged them for all their parts and "rebuilt" this box before. No more replacement parts. We didn't even have a backup either, and this box was considered somewhat important for all the scripts it ran that monitored other systems...just not "important" enough to allocate time for the Front End team to even migrate over to a VM. Since our client is so hardcore ITIL, we couldn't just do a VM on our own without proper change control procedures, a dozen sign-offs, etc.
The bunker area itself was pretty cool though; two stories underground, foot-thick old-school blast door, etc. Took me two years of asking just to finally get in and see it...real piece of history there!
Refuse to crack a phone for us? Well, well...I guess we'll just be filing a "friend of the court" against you in every case we can now. This is "banana republic" level of corruption and judicial interference.
If it's just for a small business, public facing, etc, then there are many viable suggestions already. Yet if your working on the enterprise level, inside a Microsoft AD domain architecture, the only viable choice is Sharepoint. It requires a chunk of hardware, even multiple machines, but if you have multiple internal teams that need their own CMS deploying new Sharepoint sites from a farm is pretty effective. Expensive, but effective.
If the process works better than others, should the users hurt feelings be a reason to abandon it? Unless you just handing users some beautifully finished product and don't ever have to "bother" them, their going to "hate" anything that involves any additional work. End-users originally hated the Start/Taskbar. Users hate changing passwords. Users hate IT in general. Mac users "Hate" windows. But if a process actually works better, is more efficient and delivers better than others, screw 'em. At least that's what my inner BOFH says lol.
Makes sense, since the actual security part of HIPAA is so watered-down to the point it's pretty much useless in actually requiring providers to actually do anything to secure their systems. Everything that ITSEC people would do is all considered "addressable" and not required.
ohhh ouch, and if the lab shifted or had any breach...it would be filled with water / crushed within minutes. Our current tech is not strong enough to make this feasible.
Slashdot Mirror
Was there EVER a "manually operated airbag"?
The only reason y2k didn't "happen" was because corps spent a ton of money and time fixing code and replacing computers. It wasn't just ignored and passed as a non-event. Everyone I know in IT at the time worked on various mitigation upgrades...from recoding mainframes to replacing desktops of entire companies.
Indeed, that really wasn't random either. My guess is the father was getting ready to legally take the kids away, so she flipped out and decided their better of dead than without her.
"If their busy staring into their phones and step in front of my car"
"I, Robot" is a collection of short stories. As "Golden Age" scifi it's top-of-the-line, but it's pretty outdated so any one story from it would make a pretty horrible movie. Smith's movie actually incorporates several themes and ideas from the original book. Personally, I thought the movie was quite interesting, especially the idea of "emergent behavior". We're just now using the idea in swarm programing of bots, letting them figure out their own best patterns of moving around together.
Ars has a better article, and has a map of which states are collaborators.
Unless you specifically WANT to get out of jury duty, then I suggest you saying something like "I believe in jury nullification and look forward to educating my fellow jury members if chosen for a case."
Yes, the eighth layer of the OSI model: end users. The most insecure layer of them all LOL
This comment should be +5, not 0. A close friend of mine works in ITSEC at a major research hospital. GE is one of his major headaches; their patch cycle doesn't come close to keeping the equipment secure. You can't just install any OS you want on them; nor can you just patch them at will. All of this is FDA regulated. Change anything outside of the manufacturer's allowance and you break the certification...which breaks the "warranty", support contract, and the whole insurance liability chain. A partial solution is vlans/separate physical networks...but only hospitals with $$$ can afford this. He's lucky that his workplace is very well funded (they even paid for his CISSP certs) and he has a whole team dedicated to security. Many hospitals just do the bare "Required" parts of HIPAA, which is aimed at an office manager's simple checklist.
You met John Conner's father? When The Terminator came out, Anton Yelchin was -5 years old.
Especially no President can bring back Steve Jobs, unless the next President is some type of necromancer who can raise the dead.
Did you follow through, and make the "hackers" pay for the wall?
Their using something called MyVCM to "to ensure we operate a robust information security and privacy program", whatever that actually means. I found this, which at least mentions " HIPAA, NIST, FedRAMP, COBIT, COPPA, ISO/IEC, and PCI DSS". Not sure just what particular NIST their referring to, but any company that actually pays attention to the 800 series and doesn't just go by the scant HIPAA security "regulations" is at least looking in the right direction. All of this is straight off the HIPAA Security ruling. Caremonkey won some award. Their based out of Australia.
I wouldn't use them. Because CodeMonkey comes from Australia, and, as everyone knows, Australia is entirely peopled with criminals. So you can clearly not choose the cloud-based provider in front of you.
Few people have the patients and planning capabilities to pull off what McVeigh did. It's relatively easy to go buy a gun and shoot people; making a moving truck full of home-made explosives takes time, effort, and real planning. It takes awhile to produce 5,000 pounds of explosives.
We don't have the pre-cogs to put in the vat yet for the idea in Minority Report to work lol
would you like to know more?
LOL, indeed. Your story reminds me of when I finally got to go into the "secure bunker" area of the old SABRE cold-war underground data center. Some ancient SCO box, making a horrible whining noise...a stack of other boxes of the same model next to it, we had already scavenged them for all their parts and "rebuilt" this box before. No more replacement parts. We didn't even have a backup either, and this box was considered somewhat important for all the scripts it ran that monitored other systems...just not "important" enough to allocate time for the Front End team to even migrate over to a VM. Since our client is so hardcore ITIL, we couldn't just do a VM on our own without proper change control procedures, a dozen sign-offs, etc.
The bunker area itself was pretty cool though; two stories underground, foot-thick old-school blast door, etc. Took me two years of asking just to finally get in and see it...real piece of history there!
This just in: "Batboy is new official Gawker reporter"
Sodium Hydroxide is also used in many different "recipes" as an extraction agent for making chemicals like DMT.
Shush! Stop trying to steal my tinfoil hat!
Refuse to crack a phone for us? Well, well...I guess we'll just be filing a "friend of the court" against you in every case we can now. This is "banana republic" level of corruption and judicial interference.
If it's just for a small business, public facing, etc, then there are many viable suggestions already. Yet if your working on the enterprise level, inside a Microsoft AD domain architecture, the only viable choice is Sharepoint. It requires a chunk of hardware, even multiple machines, but if you have multiple internal teams that need their own CMS deploying new Sharepoint sites from a farm is pretty effective. Expensive, but effective.
If the process works better than others, should the users hurt feelings be a reason to abandon it? Unless you just handing users some beautifully finished product and don't ever have to "bother" them, their going to "hate" anything that involves any additional work. End-users originally hated the Start/Taskbar. Users hate changing passwords. Users hate IT in general. Mac users "Hate" windows. But if a process actually works better, is more efficient and delivers better than others, screw 'em. At least that's what my inner BOFH says lol.
Makes sense, since the actual security part of HIPAA is so watered-down to the point it's pretty much useless in actually requiring providers to actually do anything to secure their systems. Everything that ITSEC people would do is all considered "addressable" and not required.
ohhh ouch, and if the lab shifted or had any breach...it would be filled with water / crushed within minutes. Our current tech is not strong enough to make this feasible.