On 26 Sep 2015 15:22:33 -0700, in bit.listserv.ibm-main you wrote: >Charles, > >I read the article, I said "what does COBOL have to do with Security"?
Probably nothing but if the applications predate the major interest in security, they may not have the proper security checking. I would have to know a lot more about the systems to take a guess as to where the problem lies. One of the scary things in many organizations is that no-one or group knows what the systems really do. They further have no good way of getting test data for fixes or good regression tests. Replacing the systems becomes a nightmare because the organizations don't really know what they are replacing. I suspect that lack of knowledge is the major cause for failed migrations to new systems. Clark Morris > >Scott > >On Saturday, September 26, 2015, Charles Mills <[email protected]> wrote: > >> "... the OPM is facing a huge problem with modernizing its security >> measures >> and tactics because of one acronym: COBOL. The programming language that >> rose to prominence in the 1960s is rampant throughout the OPM and with the >> advanced persistent threats federal agencies are experiencing, it's a >> significant vulnerability." >> >> -- http://fedtechmagazine.com/OPMhack >> >> Charles >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected] >> <javascript:;>] On >> Behalf Of Charles Mills >> Sent: Friday, September 25, 2015 10:11 AM >> To: [email protected] <javascript:;> >> Subject: Setting the writers right >> >> A recurring theme here the past couple of weeks has been the "head in the >> 1960's" writing about mainframes in news stories and now soap operas. >> >> Seriously, would it make sense for our community to put together a >> volunteer >> team (under the auspices of SHARE? Or ... ?) that would maintain a watch >> for >> stupid mainframe media putdowns and send off a packet of >> layperson-accessible education to the offending writers, editors and/or >> producers? Perhaps have a Website where writers could get current facts >> about the mainframe? Would IBM participate in some way? >> >> Any ideas? I volunteer to participate but not to lead. >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] <javascript:;> with the message: >> INFO IBM-MAIN >> > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
