Patient privacy has become a major topic of concern over the past several years. With the
majority of patient information being transferred over to digital format to improve the
convenience, efficiency and cost of storing the data, organizations expose themselves to
certain risks. These risks include the possibility of damage to the computers storing the
information by natural disaster or human mishandling, corruption by virus attacks, and even
stolen data by unauthorized personnel. Prior to the institution of the Health Insurance
Portability and Accountability Act (“HIPAA”) by Congress in 1996, there were no universal
standards set in place to identify whether or not a healthcare provider was properly securing
patient information. HIPAA was designed to reduce the administrative costs of healthcare, to
promote the confidentiality and portability of patient records, to develop standards for
consistency in the health care industry, and to provide an incentive for electronic
communications. With these standards in place, organizations better protect their systems,
and patients can feel confident that their personal medical information will remain private.

Virtually all healthcare organizations are affected by the HIPAA standards. This act applies to
any health care provider, health plan or clearinghouse (collectively “Covered Entities”) that
electronically maintains or transmits health information pertaining to patients. If you are a
Covered Entity, you must establish appropriate measures that address the physical,
technical and administrative components of patient data privacy. With the exception of small
health plans, all Covered Entities must have had data security standards in place and
operational by April 21, 2005, when the Standards for the Security of Electronic Protected
Health Information (the “Security Rule”) of HIPAA went into effect for health care providers.
Small health plans were exempted until April 21, 2006. The Security Rule requires health
care providers to put in place certain administrative, physical and technical safeguards for
electronic patient data. Among other things, Covered Entities will be required to have a Data
Backup Plan, a Disaster Recovery Plan, and an Emergency Mode Operation Plan.

Why should your organization be concerned with this compliance? Simply put,
every patient cares about the privacy and integrity of their health information. More and more
people are becoming aware of their rights to keep that data private and are taking action
when that data is compromised. With today’s dilemma of identity theft, protecting personal
information stored in digital format is critical. Baseline magazine reports that more than 90
percent of data breaches in 2006 were in digital form and some 40 percent of publicly
disclosed security breaches were caused by hackers or insider access, specifically targeting
sensitive personal information ¹. The FBI reported in 2006 that the average cost per data
breach has reached $4.8 billion and since February 2005, 93.8 million personal records have
been reported lost or stolen. With these statistics in mind, you see that not only is data
protection vital in protecting individual patients, it is also cost-effective for organizations. By
complying with HIPAA standards, you can prevent security breaches to maintain trust in your
customers as well as avoid financial loss.

What happens to organizations that do not secure their electronic protected health
information (EPHI)? HIPAA is now the law and carries serious penalties for non-compliance.
Civil penalties are $100 per violation, up to $25,000 per year for each requirement violated.
Criminal penalties range from $50,000 in fines and one year in prison up to $250,000 in fines
and 10 years in jail. Non-compliant organizations also face other serious consequences such
as losing customers and business partners who refrain from working with companies who do
not sufficiently safeguard their EPHI. Additionally, these organizations can suffer from
negative publicity and legal liabilities.

After reading this white paper, you will better understand the HIPAA data security standards
and can then compare your organization’s security with the current requirements. You will
also learn how the BloxOnline online data backup, archiving and recovery service complies
with HIPAA and can help you take a proactive approach to securing your organization’s
private data.

The HIPPA Security Rule
The Security Rule applies to protected patient health information in electronic formats. This is
protected patient information either transmitted by electronic media or maintained on
electronic media. Covered entities that maintain or transmit protected health information are
required by the Security Rule (see 45 C.F.R. §164.306) to:

• Ensure the confidentiality, integrity, and availability of all electronic protected health
information the covered entity creates, receives, maintains, or transmits.

• Protect against any reasonably anticipated threats or hazards to the security or integrity of
such information.

• Protect against any reasonably anticipated uses or disclosures of such information that are
not permitted or required under subpart E of this part.

• Ensure compliance with this subpart by its workforce.
According to the HIPAA regulations, Covered Entities are allowed to use a flexible approach
when implementing the above requirements. Specifically, Covered Entities may use any
security measures that allow the Covered Entity to reasonably and appropriately implement
the standards and implementation specifications as specified in this subpart.
In deciding which security measures to use, a covered entity must take into account the
following factors:

• The size, complexity, and capabilities of the covered entity.

• The covered entity’s technical infrastructure, hardware, and software security capabilities.

• The costs of security measures.

• The probability and criticality of potential risks to electronic protected health
information.

With this information in mind, organizations must adhere to the Security Rule’s standards
and specifications for backing up and safekeeping electronic data. Covered Entities also
need to institute a contingency plan to be prepared for an emergency – such as a natural
disaster or computer virus attack – that results in a major data loss. The contingency plan
must:

• Establish (and implement as needed) policies and procedures for responding to an
emergency or other occurrence (for example, fire, vandalism, system failure, and natural
disaster) that damages systems that contain electronic protected health information
(Administrative Safeguards – §164.308(a)(7)(i)).
This contingency plan must be implemented as follows:
• Data backup plan (Required). Establish and implement procedures to create and maintain
retrievable exact copies of electronic protected health information.

• Disaster recovery plan (Required). Establish and implement procedures to restore any loss
of data.

• Emergency mode operation plan (Required). Establish and implement procedures to
enable continuation of critical business processes for protection of the security of electronic
protected health information while operating in emergency mode.
Covered Entities must also have certain physical safeguards, such as facility access
controls. They must:

• Implement policies and procedures to limit physical access to its electronic information
systems and the facility or facilities in which they are housed, while ensuring that properly
authorized access is allowed (Physical Safeguards – §164.310(a)(1)).

• The contingency operations should establish and implement procedures that allow facility
access in support of restoration of lost data under the disaster recovery plan and emergency
mode operations plan in the event of an emergency
(§164.310(a)(2)(i)).

• In addition, Covered Entities must implement specific technical safeguards (§164.312) to,
among other things:

• Limit access to and electronic protected health information.

• Encrypt and decrypt electronic protected health information.

• Put into place audit controls that record and examine activity in information systems that
contain or use electronic protected health information.

• Implement technical security measures to guard against unauthorized access to electronic
protected health information that is being transmitted over an electronic communications
network.

These regulations are in place to ensure that healthcare organizations properly secure their
Electronic Protected Health Information (EPHI). Based on these directives, an organization
should evaluate their system and then implement a secure backup, archiving and recovery
solution to comply with HIPAA standards.

HIPPA Compliance and BloxOnline
BloxOnline online backup from SnapBlox can help organizations meet HIPAA compliance
requirements, specifically those of the Security Rule.
BloxOnline, from SnapBlox, is an online backup, archiving and recovery solution that
automates the process of securely backing up electronic data and file recovery. BloxOnline
was created, with healthcare providers in mind, to satisfy the broad need for a safe, reliable,
and cost-effective method of backing up data offsite and allowing full file restoration at any
time from any authorized location. The solution was designed to encompass the advanced
functionality and features of backup systems used by Fortune 500 companies, yet be
effortless for anyone to use regardless of their computer expertise. When BloxOnline was
unveiled to the market, it quickly gained recognition with customers nationwide, and has
since built a reputation for providing a superior quality service and world-class customer
support.

The solution ensures that all electronic protected health information (EPHI) is fully protected
when it is backed up and stored. The software encrypts all data and stores the information in
military-grade secure facilities. The HIPAA security standards require your practice to
appoint someone as the security manager³, thus only this designated individual in charge of
the security management process will have access to this data, hence preventing
unauthorized access or corruption. Furthermore, in the event of a natural disaster or system
failure, the data will be recoverable, thus, assuring that patient medical records will not be
lost.

BloxOnline Security and Encryption
Why is it important to secure and encrypt my organization’s data?
Your organization needs to protect EPHI from unauthorized access and corruption. David
Kibbe of the American Academy of Family Physicians explains, “The basic idea behind
cryptography, of which electronic data encryption is a branch, is that a group needs to keep a
message secret from everyone else and therefore encrypts it. Encryption is the
transformation of a message from plain text into nonsensical cipher text before the message
is sent. Anyone who steals the cipher text message will not be able to understand it. Only
those who have the code used to encrypt the message can convert it back from cipher to
plain text and reveal its meaning.” The following types of electronic data contain information
that should be encrypted when backed up:

• Patient billing and administrative information exchanged with payers and health plans;

• Utilization and case management data, including authorizations and referrals that are
exchanged with payers, hospitals and utilization management organizations;

• Patient health information gathered from or displayed on a Web site or portal;

• Lab and other clinical data electronically sent to and received from outside labs;

• Word -processing files used in transcription and other kinds of patient reports that are
transferred electronically;

• E -mails between physicians and patients, and between attending and referring physicians
and their offices ³.

The solution offers a secure and trusted method to protect this private data. During a backup,
all data – including patient and billing records – will be encrypted before leaving the user’s
computer(s) and is never accessible without the user’s encryption key. This encryption key is
stored only on the user’s system and never transmitted over the Internet. The backup is not
stored on the SnapBlox servers, thus SnapBlox cannot access files or even read the file
names. Only the user maintains control of their data, eliminating the threat of unauthorized
access.

The solution encrypts data using a 256-bit Advanced Encryption Standard (AES) encryption
technology. AES encryption was developed by the U.S. National Institute of Standards and
Technology (NIST) and is now the state-of-the-art standard encryption technique for both
commercial and government applications. Moreover, in June 2003, 256-AES was approved
by the United State’s National Security Agency (NSA) for use encrypting the U.S.
government’s documents classified “TOP SECRET.” Using this secure technology, data is
initially encrypted during the initial backup and then encrypted once again during the Internet
transfer.

For added security, and to meet the Security Rule’s transmission requirements, each
encrypted file is sent over the Internet via a secure channel using Secure Sockets Layer
(SSL) technology. The same Internet transmission technology is used for online banking and
credit card applications. As a result, BloxOnline is able to provide double the data encryption
of typical online backup products.

Additionally, all user data is transferred and stored in two redundant Level 4 secure data
centers, located hundreds of miles apart from each other Each data center has 24/7 onsite
monitoring, advanced security technology such as biometric access controls, backup
generators and redundant connections to the Internet.
BloxOnline Logging and Archiving

The software records each file that is backed up or restored as well as additional information
and statistics regarding the backups. This audit log, which can easily be searched, allows the
user to verify that files were successfully backed up and help troubleshoot any issues. The
user also has the option to receive an automated email notification at the conclusion of each
successful backup. Information about recent backups and total storage usage can also be
viewed via the Internet, by logging on to the user’s account. For further HIPAA compliance,
CDs and DVDs of data are available for additional archiving.
BloxOnline Logging and Archiving

The backup process and file recovery process are completely automated, eliminating the
need for manual data handling. Backups will automatically occur according to the specific
schedule the user sets in place as long as the computer is on and functioning (and not in
sleep or powersave mode). Backups can also be initiated by the user at any time. Because
backups run in the background of the system, they have little or no impact on the computer’s
performance or Internet connectivity, and are non-disruptive.
Restoring files can be accomplished with just a few clicks of the mouse by the individual who
is designated as having overall responsibility for the security of a CE’s EPHI. Using the
solution, the user simply chooses the files, folders or revisions that he or she wants to
retrieve by clicking on the file name. The data will then be downloaded to the user’s
computer, decrypted, uncompressed and then restored to their original location or another
specified location on the user’s system. A password is required to restore any files, thus,
preventing unauthorized restores, as per the HIPAA Security Rule.

In the event of a complete system failure, a full recovery of the user’s backed up data can be
initiated in just minutes. The recovery procedure can be performed on any Windows based
computer – not just the computer where the data was originally backed up. The user can
simply download and reinstall the software, enter his /her username and password, and then
enter the encryption key. Once the software installation is complete, the file catalog can be
accessed (the list of all of the files backed up) which will allow the user full control to restore
their data.

HIPPA and Your Organization
“The biggest challenge presented by HIPAA is to accurately and consistently protect
individuals’ privacy without crippling your business,” exclaims Christopher Fuller of
TechRepublic. To adhere to the standards stated in the HIPAA act while also streamlining
the implementation process, consider the BloxOnline online backup, archiving and recovery
service. BloxOnline is the ultimate solution for fully automated backups and optimum data
security. Get on the path toward HIPAA compliance and contact us to arrange for a personal demonstration.
Please note that nothing in this White Paper is intended to constitute legal advice. For more
information about HIPAA and compliance with HIPAA requirements please consult your legal
counsel.
¹ Deborah Gage and Kim S. Nash, “Case Dissection: Serious Pain,” Baseline,
December 2006
² Ponemon Institute, PGP, and Vontu, op. cit., p. 3
³ David C. Kibbe, “10 Steps to HIPAA Security Compliance,” American Academy of Family
Physicians, April 2005

We would like to welcome you to the first “State of SnapBlox” blog post. This is the first in a series of posts that will occur every three months and update our customers on the progress of SnapBlox towards its goals, projects, and any new product offerings.

For the next three months the Snapblox team will be focused on updating the portal application on enhancing and improving usability, which involved adding numerous new features, tweaking various existing ones, and adding more subtle changes to make the system simpler & more efficient to use.

Great news, we modified the way our email servers send outbound by adding Google Postini Message Security to filter outbound only messages from SPAM and Viruses. With this new service in place we can help reduce SPAM outbound from our servers and prevent our IP address from being blacklisted.  We can also offer this service inbound to help reduce inbound SPAM and Virus and provide a daily summary of potentially SPAM. Check out www.snapblox.com/google-postini-message-security.php to learn more on Inbound and Outbound Message Security Service.

Did you notice our new chat service to contact Sales or Support, this is a new service we are testing out to provide you with a way to contact our departments.  Again to recap we offer a toll free number (866-524-7707), support forms using the portal and now online chat.

If you have any questions please post in the comments or contact your local sales rep.

Thanks, Michael
SnapBlox CEO and President

Synopsis:
This documentation assumes that you have a version of Cisco IOS that supports the following MIB ciscoNbarProtocolDiscoveryMIB (1.3.6.1.4.1.9.9.244). This documentation assumes that (MRTG) Multi Router Traffic Grapher is installed and working. This documentation assumes that you have SNMP installed and working. This documentation assumes that you have used custom mrtg.cfg files.

What is NBAR?
Network Based Application Recognition is an intelligent classification engine that recognizes applications that are static (which use fixed TCP or UDP port numbers), and stateful (which dynamically assign TCP or UDP port numbers).

The NBAR Protocol Discovery Management Information Base (MIB) expands the capabilities of NBAR Protocol Discovery by providing the following new Protocol Discovery functionalities through SNMP:

What is MRTG?
MRTG consists of a Perl script which uses SNMP to read the traffic counters of your routers and a fast C program which logs the traffic data and creates beautiful graphs representing the traffic on the monitored network connection. These graphs are embedded into webpages which can be viewed from any modern Web-browser.

In addition to a detailed daily view, MRTG also creates visual representations of the traffic seen during the last seven days, the last five weeks and the last twelve months. This is possible because MRTG keeps a log of all the data it has pulled from the router. This log is automatically consolidated so that it does not grow over time, but still contains all the relevant data for all the traffic seen over the last two years. This is all performed in an efficient manner. Therefore you can monitor 200 or more network links from any halfway decent UNIX box.

MRTG is not limited to monitoring traffic, though. It is possible to monitor any SNMP variable you choose. You can even use an external program to gather the data which should be monitored via MRTG. People are using MRTG, to monitor things such as System Load, Login Sessions, Modem availability and more. MRTG even allows you to accumulate two or more data sources into a single graph.

Enable NBAR in IOS:

!
router#
Interface FastEthernet 1/0
Router(config-if)#ip nbar protocol-discovery
!

Test for Supported MIB:

snmpwalk -c COMMUNITY -v2c IPADDRESS 1.3.6.1.4.1.9.9.244
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.2 = INTEGER: 2
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.3 = INTEGER: 2
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.4 = INTEGER: 2
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.1 = Timeticks: (1537) 0:00:15.37
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.2 = Timeticks: (0) 0:00:00.00
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.3 = Timeticks: (0) 0:00:00.00
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.4 = Timeticks: (0) 0:00:00.00
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.1 = STRING: “ftp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.2 = STRING: “http”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.3 = STRING: “egp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.4 = STRING: “gre”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.5 = STRING: “icmp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.6 = STRING: “eigrp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.7 = STRING: “ipinip”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.8 = STRING: “ipsec”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.9 = STRING: “bgp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.10 = STRING: “cuseeme”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.11 = STRING: “dhcp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.12 = STRING: “dns”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.13 = STRING: “finger”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.14 = STRING: “gopher”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.15 = STRING: “secure-http”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.16 = STRING: “imap”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.17 = STRING: “secure-imap”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.18 = STRING: “irc”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.19 = STRING: “secure-irc”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.20 = STRING: “kerberos”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.21 = STRING: “l2tp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.22 = STRING: “ldap”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.23 = STRING: “secure-ldap”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.24 = STRING: “sqlserver”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.25 = STRING: “netbios”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.26 = STRING: “nfs”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.27 = STRING: “nntp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.28 = STRING: “secure-nntp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.29 = STRING: “notes”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.30 = STRING: “ntp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.31 = STRING: “pcanywhere”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.32 = STRING: “pop3″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.33 = STRING: “secure-pop3″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.34 = STRING: “pptp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.35 = STRING: “rip”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.36 = STRING: “rsvp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.37 = STRING: “smtp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.38 = STRING: “snmp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.39 = STRING: “socks”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.40 = STRING: “ssh”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.41 = STRING: “syslog”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.42 = STRING: “telnet”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.43 = STRING: “secure-telnet”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.44 = STRING: “secure-ftp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.45 = STRING: “xwindows”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.46 = STRING: “printer”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.47 = STRING: “novadigm”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.48 = STRING: “tftp”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.49 = STRING: “exchange”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.50 = STRING: “vdolive”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.51 = STRING: “sqlnet”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.52 = STRING: “rcmd”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.53 = STRING: “netshow”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.54 = STRING: “sunrpc”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.55 = STRING: “streamwork”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.56 = STRING: “citrix”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.57 = STRING: “napster”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.58 = STRING: “fasttrack”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.59 = STRING: “gnutella”
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.60 = STRING: “kazaa2″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.61 = STRING: “custom-01″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.62 = STRING: “custom-02″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.63 = STRING: “custom-03″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.64 = STRING: “custom-04″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.65 = STRING: “custom-05″
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.66 = STRING: “custom-06″

Not Supported MIB in IOS

snmpwalk -c COMMUNITY -v2c IPADDRESS 1.3.6.1.4.1.9.9.244
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (SNMPv2-SMI): At line 0 in (none)
Cannot find module (UCD-SNMP-MIB): At line 0 in (none)
Cannot find module (UCD-DEMO-MIB): At line 0 in (none)
Cannot find module (SNMP-TARGET-MIB): At line 0 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
Cannot find module (SNMPv2-TM): At line 0 in (none)
.iso.3.6.1.2.1.1.3.6.1.4.1.9.9.244 = No Such Instance currently exists

Examples from the following output:

snmpget -c COMMUNITY -v2c IPADDRESS 1.3.6.1.4.1.9.9.244.1.2.1.1.2.1.1
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.interface-number.protocol
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1 – FastEthernet 1/0
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.1 – FTP Protocol Number

The nbar-internet.cfg file assumes that you are monitoring FastEthernet 1/0. Change this to refelect the interface you are monitoring.
Change public@isp1 to the correct community string and ip address.

Create New Directory:
Create the following directory under mrtg web files.

nbar-internet

Files Created:
The above configuration will create the following files under nbar-internet directory.

fasttrack.log
ftp.log
gnutella.log
h323.log
http.log
https.log
kazaa2.log
napster.log
nntp.log
pop3.log
rstp.log
smtp.log
streamworks.log
vdolive.log

MRTG CFG FILE: (nbar-internet.cfg)
Download nbar-internet.cfg

### Global Config Options
Options[_]: growright,bits
WithPeak[_]: ymw
Xsize[_]: 600
Ysize[_]: 200
Ytics[_]: 10

##
## FTP Traffic Analysis
##
Target[nbar-internet-ftp]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.1&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.1:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.1&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.1:public@isp1:
SetEnv[nbar-internet-ftp]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-ftp]: nbar-internet
MaxBytes[nbar-internet-ftp]: 1000000
Title[nbar-internet-ftp]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-ftp]:

##
## HTTP Traffic Analysis
##
Target[nbar-internet-http]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.2&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.2:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.2&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.2:public@isp1:
SetEnv[nbar-internet-http]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-http]: nbar-internet
MaxBytes[nbar-internet-http]: 1000000
Title[nbar-internet-http]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-http]:

##
## HTTPs Traffic Analysis
##
Target[nbar-internet-https]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.15&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.15:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.15&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.15:public@isp1:
SetEnv[nbar-internet-https]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-https]: nbar-internet
MaxBytes[nbar-internet-https]: 1000000
Title[nbar-internet-https]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-https]:

##
## smtp Traffic Analysis
##
Target[nbar-internet-smtp]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.37&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.37:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.37&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.37:public@isp1:
SetEnv[nbar-internet-smtp]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-smtp]: nbar-internet
MaxBytes[nbar-internet-smtp]: 1000000
Title[nbar-internet-smtp]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-smtp]:

##
## NNTP Traffic Analysis
##
Target[nbar-internet-nntp]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.27&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.27:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.27&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.27:public@isp1:
SetEnv[nbar-internet-nntp]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-nntp]: nbar-internet
MaxBytes[nbar-internet-nntp]: 1000000
Title[nbar-internet-nntp]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-nntp]:

##
## vdolive Traffic Analysis
##
Target[nbar-internet-vdolive]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.50&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.50:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.50&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.50:public@isp1:
SetEnv[nbar-internet-vdolive]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-vdolive]: nbar-internet
MaxBytes[nbar-internet-vdolive]: 1000000
Title[nbar-internet-vdolive]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-vdolive]:

##
## streamworks Traffic Analysis
##
Target[nbar-internet-streamworks]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.55&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.55:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.55&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.55:public@isp1:
SetEnv[nbar-internet-streamworks]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-streamworks]: nbar-internet
MaxBytes[nbar-internet-streamworks]: 1000000
Title[nbar-internet-streamworks]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-streamworks]:

##
## napster Traffic Analysis
##
Target[nbar-internet-napster]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.57&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.57:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.57&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.57:public@isp1:
SetEnv[nbar-internet-napster]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-napster]: nbar-internet
MaxBytes[nbar-internet-napster]: 1000000
Title[nbar-internet-napster]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-napster]:

##
## fasttrack Traffic Analysis
##
Target[nbar-internet-fasttrack]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.58&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.58:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.58&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.58:public@isp1:
SetEnv[nbar-internet-fasttrack]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-fasttrack]: nbar-internet
MaxBytes[nbar-internet-fasttrack]: 1000000
Title[nbar-internet-fasttrack]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-fasttrack]:

##
## gnutella Traffic Analysis
##
Target[nbar-internet-gnutella]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.59&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.59:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.59&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.59:public@isp1:
SetEnv[nbar-internet-gnutella]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-gnutella]: nbar-internet
MaxBytes[nbar-internet-gnutella]: 1000000
Title[nbar-internet-gnutella]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-gnutella]:

##
## kazaa2 Traffic Analysis
##
Target[nbar-internet-kazaa2]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.60&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.60:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.60&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.60:public@isp1:
SetEnv[nbar-internet-kazaa2]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-kazaa2]: nbar-internet
MaxBytes[nbar-internet-kazaa2]: 1000000
Title[nbar-internet-kazaa2]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-kazaa2]:

##
## H323 Traffic Analysis
##
Target[nbar-internet-h323]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.75&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.75:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.75&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.75:public@isp1:
SetEnv[nbar-internet-h323]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-h323]: nbar-internet
MaxBytes[nbar-internet-h323]: 1000000
Title[nbar-internet-h323]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-h323]:

##
## rstp Traffic Analysis
##
Target[nbar-internet-rstp]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.71&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.71:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.71&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.71:public@isp1:
SetEnv[nbar-internet-rstp]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-rstp]: nbar-internet
MaxBytes[nbar-internet-rstp]: 1000000
Title[nbar-internet-rstp]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-rstp]:

##
## pop3 Traffic Analysis
##
Target[nbar-internet-pop3]:
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.32&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.32:public@isp1 +
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.32&1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.32:public@isp1:
SetEnv[nbar-internet-pop3]: MRTG_INT_IP=”" MRTG_INT_DESCR=”"
Directory[nbar-internet-pop3]: nbar-internet
MaxBytes[nbar-internet-pop3]: 1000000
Title[nbar-internet-pop3]: Cisco Nbar Protocol Analysis
PageTop[nbar-internet-pop3]:

Additional References:

Cisco IOS images that support CISCO-NBAR-PROTOCOL-DISCOVERY-MIB MIB.
[...]

Network-Based Application Recognition and Distributed Network-Based Application Recognition:
[...]

Network-Based Application Recognition Protocol Discovery Management Information Base:
[...]