There may be more entry points to your system than you know

This is an example of a remote client that connects to an interactive qsh session on the server. Although this example requires QSHELL (on the server), and the client requires either AIX or Linux, the concept is simple: A host based program that opens a socket, listens to connections, and executes commands.

A diligent reader can Google a few more samples in a short time.

How to protect yourself from those rogue access points?

1. Use NETSTAT OPTION (*CNN) to review all of the existing open ports.

2. Create TCP port restrictions on all ports that you do not plan to use.

3. Audit your system carefully.

Of course, if you are willing to have the best protection and ready to work hard to achieve it, you can place a firewall between your iSeries server and the rest of the corporate network.

==================================
MORE INFORMATION ON THIS TOPIC
==================================

The Best Web Links: tips, tutorials and more.

Search400's targeted search engine: Get relevant information on security.

Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.

Check out this Search400.com Featured Topic: Top ten security tips

Visit the ITKnowledge Exchange and get answers to your security questions fast.

Rate this Tip To rate tips, you must be a member of Search400.com. Register now to start rating these tips. Log in if you are already a member. Digg This!     StumbleUpon     Del.icio.us    RELATED CONTENT Systems Management Can you trust all those trigger programs? Are your backups complete? Controlling remote command processing Time for your annual checkup Watch your profiles Avoid locking issues Send message to users at a remote site Security journal receiver management Top 10 backup commands Tracking critical file access in real time iSeries security tips Security monitoring on IBM i: Watching your super users Tracking System i program object changes Recovering your AS/400 security configuration System values on i: Setting them up and locking i down A guide to System i security, Part 3: Digging in to the System i security environment Is your AS/400 secure?: How a hacker could get valuable information from your system System i security report round-up A guide to System i security, part 2: Landing and establishing access Creating a System i database security policy: Implementation A guide to System i security: Descending into the heart of darkness of IT security iSeries system and application security Security monitoring on IBM i: Watching your super users Tracking System i program object changes More consolidation in the i world: Audax purchases Bytware Recovering your AS/400 security configuration System values on i: Setting them up and locking i down A guide to System i security, Part 3: Digging in to the System i security environment Primary group authority: How it works Blocking access to SQL line commands Moving files to new libraries allows access to only groups or users that are authorized Changing telnet ports: A security solution? RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary midrange  (Search400.com) RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.