November 28, 2012 at 1:15 am
Comments posted to this topic are about the item Regulators, Mount Up
November 28, 2012 at 1:27 am
Regulation is a cloud that can have a bright silver lining.
Lets suppose that you have old systems ridden with tech debt and propped up by manual processes.
Those powers that be are so used to the situation that the idea that the tech debt or the manual processes are a problem just doesn't register. They are chasing the new shiny ball.
All of a sudden regulation comes along and lifts up the rock and shines a bright light underneath it and reveals the superating horrors squirming underneath!
Too many people have too much access to too much data almost certainly meaning a failed regulatory audit.
All of a sudden you have the impetus and support to fix a load of old problems and simplify the way your systems work. Do this well and not only will you pass regulatory inspection but you will also demonstrate the art of the possible, how good things could be if the prime focus was delivering something maintainable, scalable, flexible.
November 28, 2012 at 2:14 am
@david-2: Wow, nice inspiring post on what I thought was a fairly turgid topic. I feel more motivated to get on with my day's battle against the systems already. I guess you are saying to look for the opportunity in everything - and you know what, you're right, otherwise this job ends up just being a pile of crud.
November 28, 2012 at 5:26 am
If you know like I know you don't wanna step to this.
Cheers
November 28, 2012 at 6:10 am
jfogel (11/28/2012)
If you know like I know you don't wanna step to this.
Then I suggest you find alternate employment. This is a big deal to people whose data you handle.
Steve, thank you for spelling HIPAA correctly, four times no less! (it's the little things) Some people can't even get it right on their resumes...
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
November 28, 2012 at 6:27 am
Hey dummy, look it up. Its part of the song.
Cheers
November 28, 2012 at 6:32 am
jfogel (11/28/2012)
Hey dummy, look it up. Its part of the song.
I apologize for taking your statement as a statement, rather than being hip to your bad music. Carry on.
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
November 28, 2012 at 6:38 am
Yes, its "my bad music" because I chose the title to the article. You aren't doing well this morning on this one so I suggest you let it go.
Cheers
November 28, 2012 at 8:02 am
jcrawf02 (11/28/2012)
Then I suggest you find alternate employment. This is a big deal to people whose data you handle.
I can enthusicastically agree with jcrawf02 here on these concerns. I've had my data exposed by people who really didn't care that much and I don't like it one bit. I'm sure accidents happen, mistakes are made, but any emphasis toward security here made by anybody gets my vote.
Security should be part of anybody's job who work in information technology, and not relegated to a few select specialties. I've heard all too many times that securing this or that is "not my job."
November 28, 2012 at 8:25 am
What is it exactly that has anyone thinking I don't care about data security? I quoted a line from the song that made up the title of the editorial and nothing more. Next I guess it will be that not only could I care less about security I kick puppies and steal from the elderly.
Cheers
November 28, 2012 at 8:46 am
So, the topic of data encryption comes up every day in my daily duties. More so than earlier in my travels when folks were oblivious to what was stored in the data layer nor cared about how it was stored, just who and what systems had access to "the data". I'm now delighted to hear business units actively address secure data access AND encrypted data. One of the most surprising dialogs was between a VP of Marketing (whose interest was in mining customer data), a 3rd party resource (who was designing the middleware) and architects actually PLANNING to improve the data hardware to compensate for overhead need to encrypt data as well as designating what data elements needed to be encrypted.
How does this help me as the DBA in these instances? It's a excellent step towards insuring that whatever measures we take to secure the data are understood and done with a suitable level of transparency that everyone in the project is comfortable with and that's a good thing.
I'm only saying this to say that increased awareness and implementation of encryption, albeit a bit more work, is an excellent topic well worth the resources spent.
By the by, kudos for the song references. Still don't think this album got the recognition it
deserves may throw it on the playlist-of-the-day just because...
November 28, 2012 at 9:17 am
Its amazing what happens if you wave the possiblity of nuking old dead systems in front of a DBA. Their wrinkles vanish, an unfamiliar expression (happy smile) crosses there face and they hit keys faster than a teenager in a Halo death match.
I suspect I may have started something here!
November 28, 2012 at 9:55 am
One note on encryption. I heard a discussion from some devs and architects that were under the impression that encryption would prevent sql injection issues. Not likely to happen, so be sure that good coding practices are still being followed.
November 28, 2012 at 10:54 am
It's not just unencrypted data that auditors ding you on nowadays. Wearing many hats at once and doing things outside your job description can definitely get you dinged as well. SarBox standards are very picky on this nowadays..For example, we had an IT guy once caught moving furniture around in his cube and the auditors jumped all over that with managment and the man was reprimanded over it. Not in his job description, don't do it again. If you are a little shop you can still get away with a "Jack-of-all-trades" guy (I don't know for how long though), but that is no longer permitted at most larger shops or government agencies that fall under the strict auditing standards of today. Heck, the auditors dinged us for having our production clusters on the second node, left there after a failover!!!!! Picky, picky...:-D
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
November 28, 2012 at 3:20 pm
I have been through several SOX audits and have never heard of that. I would have have said stick it, see the job description says "and other duties as required" which I think is in every single job description I have seen for years. The whole point of SOX is to document what you do and how you do it and make sure everyone knows (including shareholders and regulators). It has always seemed overblown to me. Next they'll say you can't get up to get water to quench your thirst because you have to operate the water fountain.
Viewing 15 posts - 1 through 15 (of 27 total)
You must be logged in to reply to this topic. Login to reply