Hot on the heels of the Network Security 6.0 release, I sat down with Jill Martin to discuss events leading up to the launch.
Hi Jill! Thanks for giving me some time this morning to talk about NS 6. Webinar attendees probably know you well, but why don’t you give us a quick introduction?
Sure! My name is Jill Martin and I am the PowerTech Product Support Manager. I have been with Help/Systems for about twelve years and have worked in a number of capacities, including product trainer, sales representative, and most recently as part of the PowerTech team.
So, tell me what responsibilities you have as Product Support Manager?
As manager of the technical support staff, one of my main roles is overseeing the support you receive if you ever call in to PowerTech. I also worked closely with the development team over the last couple of months to prepare for the release of Network Security version 6.0.
So what is the big “hook” with Network Security version 6?
A couple of things really. First, we added the ability to set rules based on an object. What I mean by that is that we have created the incredibly powerful capability to be able to set rules that pertain to an object. This means it’s now possible to restrict and audit access to an object regardless of the syntax of the incoming request. In SQL for example, Select fld1, fld2 from myfile was previously seen as a different request than select fld1 from myfile. As humans, we could look at that and know it was pulling the same data, but the server couldn’t. This capability adds to the powerful transaction-based rules that Network Security has long been admired for.
We also have added a new selective activation process, so customers can decide which exit points are secured. This allows a staged approach to integrate Network Security into the operating system, something that is often important in large IT shops.
In addition, we have done a lot of infrastructure changes to ensure that the product works efficiently, and that the user interface is more intuitive. Some of these changes won’t really be seen directly by customers, but they are an important part of planning for future enhancements that we are designing.
Did we have dedicated programmers working on this product?
On a project of this size, we assign a lead developer who oversees the development aspect of the project. Obviously that is someone who is intimately familiar with the PowerTech Network Security solution. We also have other developers that are familiar with security solutions and have additional resources who are are assigned “as needed,” based on the tasks identified in the project plan. Of course, these folks all report through the development chain to a manager who is responsible for product design and coding.
So how do you test a pending product release?
All Help/Systems products go through a stringent testing process that includes unit testing, integration testing, systems testing, and acceptance testing. We have a number of dedicated testers—people whose sole job is to test new development projects. They build a test plan and divide up the different sections between themselves. There is also a support person involved because they know what customers want and how they use the software. Gregg Bury was the support person, and he spent some time reviewing the functionality and the usability of the interface, and making recommendations on improvement.
So what things did the testers look at?
They tested the changes and did regression testing to the core product to review every panel and function to identify whether there were any outstanding issues from prior releases. They also did performance and stress testing using scripts.
Did they test at every release level?
Absolutely, they tested at every release that we support—currently V5R4, V6R1, and V7R1
Presumably as the testers locate issues, they prioritize them?
They do; they rank items using a priority scheme and those with a priority 1 or 2 are the things that were addressed first.
As far as making the code available to customers, how is that done?
Well, the download page has already been updated to show the new level of the code. As far as getting the code onto a customer’s machine, that is one of the changes between the last release of 5.3 and the current release of 6.0. In 5.3, we had a save file that was downloaded to a PC and then manually extracted, sent to the server, and installed from there. With version 6.0, we have a self-extracting installer. It uploads and installs the code on the server, and performs the cleanup, leaving only the administration guide on the user’s PC.
Does the customer have to know anything about their configuration to perform that install?
Yes, they need to sign on with a user profile that has the necessary authority to perform an upload and a restoration of the application. The Installation Guide walks them through the necessary requirements and steps.
So there is a new Administration Guide?
Yes, there is.
Where can existing customers find it?
They can go to the support area of the PowerTech website, under the “customer login” link in the top navigation bar. The documentation is all listed at the top of the product download page. If someone doesn’t remember their support log-in, they can contact support at support@powertech.com
Did we do a BETA program?
Well, typically Help/Systems does more of a managed release or limited ship. We do not like to give a product to customers until we feel we are on top of the release. In this case, we had a few customers who offered to help because they needed one or more of the new features. So, we had a few people using the product and giving us feedback.
How do existing v5.x customers upgrade to Network Security version 6?
The product installs into a new library, which allows the system to remain protected during the installation process. There is a command to merge rules into Network Security version 6, and the activation process allows the redirection of the exit programs to the new version in the new library.
What do the developers do after a product is released?
First they celebrate! Then they go through a number of post-project processes. There is a documentation review to analyze our methodologies and to make any necessary improvements going forward. After that, they begin to look at the next project and the development manager re-deploys the development resources based on the next project plan. The good news/bad news with working for a company as creative as Help/Systems is that we never rest. In fact, there are already requirement lists for Network Security 7.0 that we are looking at.
Where can customers learn more about Network Security 6.0?
There is a “new features” document that is a great place to start. It shows what’s new, and what’s changed. For example, the authorization lists that we use to define the capabilities of the administrators have changed names. A customer will want to review who has access to the product—the documentation discusses all of that.
We are planning to do a “What’s New” Webinar in the coming weeks to talk about the new features in Network Security 6.0. Our Web-based Network Security training class will be based on version 6.0 later this year.
What about support of the new product version?
The support staff have all been trained on the new version and have been working with the software on our internal systems, as well as with the “early-ship” customers. Our international staff have also been working with the new version.
Any closing thoughts?
Just that we are very excited to have this new Network Security release now shipping. And, I’m looking forward to building the feature list for the next release.
So there you have it—an introduction to a PowerTech product release. If you have any extra questions for Jill, please send them to jill.martin@powertech.com
Cheers!
- rt
Robin Tatam is the Director of Security Technologies for PowerTech, a leading provider of security solutions for IBM i. A frequent speaker on security topics, he co-authored the RedbookIBM System i Security: Protecting i5/OS Data with Encryption. Robin can be reached by e-mail at robin.tatam@powertech.com.
Jill Martin is Product Support Manager for PowerTech and brings a strong System i background to any security discussion. Jill has worked in a number of roles in the industry, including technical trainer, sales account manager, and most recently as a key member of the security team. Contact Jill at jill.martin@powertech.com.
Paul “Paulie” Culin is a security advisor with the PowerTech Group. As a product expert, he manages client training and implementation engagements, and hosts security presentations, Webinars, and product demonstrations. Contact Paul at 
I am in Central Florida this week to attend the 50th Anniversary COMMON annual meeting and exposition, hosted at the Orlando Marriott resort. This is my first time touching down in Florida, and I have not been disappointed. Although I do not have the complexion to ever consider becoming a “sun worshipper,” there is an immediate recognition of why this state attracts thousands of visitors from around the world: Clean streets, pristine buildings, and endless entertainment and activities for people of every age. I arrived a couple of days early and drove over to Cocoa Beach, and then down to West Palm Beach to visit my “brother” from my time as a foreign exchange student. It was wonderful to reconnect with him after a couple of years.