Make sure you properly secure the HMC. Paul Robichaux (from NewEra Software) and Barry Schrager (from xBridge Systems, and ACF2 fame) did a presentation at Share in San Francisco in 2013 titled 'The HMC is a Fantastic Tool But Are You Making It Secure?' Session 12255. They had found a number of customers who were using the remote access, but they didn't realize some of the exposures that remote access introduced.
Greg Boyd Mainframe Crypto (www.mainframecrypto.com) On Tue, 5 Aug 2014 20:28:55 +0000, Ken Porowski <[email protected]> wrote: >Any reason to prefer one setup over the other? > >Local (my office) HMC connected to remote datacenters (50+ miles and 200+ >miles) > >Remote access (from my office) to an HMC in remote datacenters (50+ miles and >200+ miles) > > >I�m going to have 2 datacenters (200+ miles apart) in CoLo providers >Closest datacenter will be within 50 miles of the office where I work >Intent is to have only �smart� third party support access to the datacenter >(for racking/cabling/rebooting) >Mainframe activity (IPL/POR) to take place remotely with fallback to �smart� >third party support if needed. >Rack space will be at a premium so they don�t want to waste it on an HMC if >they can avoid it. > >Thanks all for your input. >Ken > > >Ken Porowski >VP Mainframe Engineering >CIT >Information Technology >One CIT Drive >Livingston, NJ 07039 >+1 973 740 5459 (tel) >[email protected]<mailto:[email protected]> >www.cit.com<http://www.cit.com> > > > > > >This email message and any accompanying materials may contain proprietary, >privileged and confidential information of CIT Group Inc. or its subsidiaries >or affiliates (collectively, �CIT�), and are intended solely for the >recipient(s) named above. If you are not the intended recipient of this >communication, any use, disclosure, printing, copying or distribution, or >reliance on the contents, of this communication is strictly prohibited. CIT >disclaims any liability for the review, retransmission, dissemination or other >use of, or the taking of any action in reliance upon, this communication by >persons other than the intended recipient(s). If you have received this >communication in error, please reply to the sender advising of the error in >transmission, and immediately delete and destroy the communication and any >accompanying materials. To the extent permitted by applicable law, CIT and >others may inspect, review, monitor, analyze, copy, record and retain any >communications sent from or received at this email address. > > > > >---------------------------------------------------------------------- >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
