Internet of Things: You Can’t Avoid the Inevitable

Internet of Things - Other
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times


This article is excerpted from Identity Management: A Business Perspective, chapter 7.

The Internet of Things (IoT) is upon us. “What does that mean?” you may ask. Well, it means you had better get ready to use your identity management environment to support access to “things.” “But we don’t do that,” you reply. “Why not?” is my response. It is highly likely that there are business processes within your organization that could benefit from the deployment of things. So when you finally get pulled into the 21st century, you will need to plan for more than just people accessing your systems.

Over the past few years, we have experienced a dramatic reduction in the cost of devices that monitor things and actuators that control things. It is now very inexpensive to remotely measure things and to turn things on and off. It’s important that companies evaluate the potential of exploiting these cost reductions and take advantage of the opportunity that they afford.

But before you invest in IoT, there are a few questions you will need to answer, as shown in Table 7.1

Table 7.1: Questions to ask when assessing IoT

Collection Devices

Control Devices

How will you associate ownership with collected data?

Who should be able to access control devices?

How will you protect data, and how will you give owners access to it?

What level of access should approved users be given?

How will you allow users to share data with authorized persons?

Should users be able to delegate access to others?

If you can answer these questions, improvements to numerous business applications await.

Devices as Things

So the next question is: “What’s a ‘thing,’ and what does it want?”

Things can basically be divided into two categories: those that can measure something (sensors) and those that control something (actuators). Sensors can be as simple as a thermometer that measures the temperature inside a house, or as complex as the monitor that measures a car’s fuel mixture as the vehicle accelerates.

In a manufacturing environment, IoT data can be very valuable. IoT data can, for example, show how much product is being produced and the rate of rejects, how many people are on a ship’s bridge and their ranks, or the current rate of inventory depletion, and project when the manufacturing department will run out of raw material. Increasingly, we need to share this data with others in the company or business partners outside the company. How do we control the release of sensitive information, and how do we restrict its usage to approved persons?

Actuators are even more interesting. They can either be discrete, turning something on or off, or they can be a continuous process-control device such as a valve moderating the flow of a gas, liquid, or granular solids in accordance with external stimuli. Adding cement, aggregate, and water into a cement mixer is an example. It should be obvious that restricting access to actuators to authorized personnel is very important.

Contributing Technologies

It is fortunate that IoT technology is developing at a time in which related services are becoming available. Not only are manufacturing economies of scale driving down the cost of devices, other technology developments are contributing to the economic viability of IoT installations.


There are multiple areas in which the cloud contributes to IoT deployments. Data storage is one area to be addressed in any installation of IoT devices. In some cases, where data volumes are large, it makes sense to store data in the cloud, where the requisite encryption is facilitated and the business continuity services offered by cloud service providers (CSPs), such as data backup and restore, can be leveraged.

It is arguably also easier to manage access to data in the cloud. With on-premises databases, there is a requirement to configure the access control settings for the database or put the data store on a protected subnet. In the cloud, user access can be restricted by the cloud service access control facility based on an attribute in the user’s directory entry.

A CSP can also perform a useful communications task for companies with industrial computer installations with remote monitoring facilities. CSPs with multiple data centers can be used to collect data from remote monitoring points close to one facility and make it available via a data center close to the company’s administration point.

Big Data Analysis

Sometimes devices produce a lot of data that needs to be analyzed either continuously or periodically for trends or to identify significant events. Here cloud-based services can be advantageous. Hadoop analysis and map-reduce functionality are easier to deploy in the cloud and can facilitate turning raw data into information for managers tasked with understanding IoT data and making appropriate management decisions.


It’s generally agreed among industry analysts that we are heading toward a catastrophe with IoT technology; it could be corporate but will more likely occur in the public sector. It will probably entail unauthorized access to sensitive data that is subsequently released to nefarious persons, or it may be a malicious attack on a control device resulting in inappropriate messages being sent to an industrial process. The result will be unprecedented regulation being imposed on IoT systems. It will be the classic “closing the gate after the horse has bolted” syndrome and will happen because:

  • Those in authority in this technology space are abrogating their responsibility to understand and impose governance over IoT. This is most unfortunate because it does not need to happen: plenty of help in the form of information and tools is available, and there are enough people who know how to use them.
  • Those with regulatory authority fail to develop regulation until they have to. This, too, is most unfortunate because we know what can go wrong, and we have the technology to stop things from going wrong. Industry is quite capable of working with government to ensure that regulation is sufficient and fit-for-purpose; waiting until there’s a political expediency means regulation will likely be draconian and expensive.

But it’s not all doom and gloom. There are some bright spots that we will come to soon.

Best Practices

There are a number of areas in which organizations should plan their IoT implementations to optimize their usefulness and avoid potential problems.

Data Management

Data from sensors must be securely collected and adequately protected in storage. The data communication channel must be managed, and appropriate notifications should be issued. For instance, for temperature measurements, periodic transmissions are adequate with only averages stored for any length of time. However, if a temperature reading is outside normal ranges, an alarm should be raised. 

Depending on the sensitivity of the data, it might be necessary to digitally sign the transmission of data collected so that the receiver can be sure it originated at the prescribed sensor. Or the data might be encrypted to ensure that the message can’t be intercepted and understood.

It is also necessary to define controls on data being written to corporate systems. If Web services are being used, the HTTP method(s) that can write—to a database, for instance—and the conditions placed on it should be documented. For high-security environments, APIs should be used that define the data that can be passed through the interface and what can be done with it. For instance, a popular data transfer mechanism is an XML file using a signed SOAP message. If the message is not appropriately signed, it will not be actioned, and if the XML file does not use the prescribed tag names, the data will not be written to the protected repository.

Note: Enterprise data store interface protocols such as SQL or LDAP should not be deployed in a cross-boundary environment. If data is originating from a remote location, the use of an API is highly recommended. In this way, the appropriate API security, which ensures the confidentiality and integrity of the data, and API management, which ensures that governance processes are observed, will be implemented. When it comes to actuators, it is most important to adequately restrict access to these devices. If a device can be controlled by an unauthorized person, a potential catastrophe is enabled.

Device Categorization

Device capability, management requirements, and security controls vary widely depending on their “category.” A controller in an in-house production line has a different security profile from the HVAC thermostat. Data from the production management system has a different sensitivity than the research results from the latest pharmaceutical trials. Categorization will ensure appropriate treatment of access control to devices and data from devices. This, in turn, will ensure that IoT infrastructure is not over-engineered, which adds costs, or under-engineered, which could possibly expose the organization to unnecessary risk.

Next Steps

So, how should organizations exploit this potential? What can be done to make sure companies don’t miss the opportunities that arise?

Step 1: Strategy Development

The most important step in exploiting IoT is developing a strategy. Without this step, there will be no appreciation of the potential of IoT to assist the organization and therefore no development of competitive advantage based on the potential of “things” to improve business processes.

Worse still, some business units within the organization might decide to “go it alone” and develop IoT facilities without implementing the proper controls or a plan for wider development in the company. This is dangerous because there will be no management oversight of interfaces that are developed, resulting in exposure of the company to unnecessary risk and potential damage to corporate infrastructure and potentially the community.

Ideally, IoT integration should be within the controls established for technology integration in the corporation’s enterprise architecture. IoT devices should be addressed at the technology level to give business units guidance on supported device types so that there is not a plethora of different devices deployed within the organization. At the application level, APIs for device integration should be determined with management and security requirements stipulated. At the information level, the device integration should be addressed with direction given for database interfaces and data management controls. At the business level, the processes impacted by IoT devices should be determined with consideration given to wider deployment of IoT technology or sharing of IoT data with a wider audience.

Interfaces to the identity management and access control facilities should be addressed at the information architecture level.

Strategy must, by definition, include an environmental scan that determines the current situation. This will include documenting current capabilities and desired goals, and possibly a SWOT analysis to identify the weaknesses to be overcome and the opportunities to be exploited.

This must include a definition of how IoT will integrate with the IdM environment.

Step 2: Capability Development

There’s little point in developing a strategy if there’s no capability to put it into action. Organizations might have IoT expertise on staff— particularly if they are managing a production environment, these staff should investigate the opportunity to extend their manufacturing system to provide better data or controls to business unit personnel. In the event that there is no in-house expertise, it will need to be brought in or developed. In the event that a system integrator is engaged to deploy an IoT system, reliance on the supplier might well be the best approach, but this must be done within the constraints of the company’s policy and practices. It is important to ask the right questions so that the organization’s commercial integrity and intellectual property are protected.

Step 3: Infrastructure Deployment

The deployment step is a standard project-management exercise:

  • Plan—Investigate options and develop a project plan.
  • Design a solution—This will include understanding the business unit requirements and documenting the desired outcomes.
  • Deploy the technology—This will include an interface to the organization’s IAM environment to manage access controls.
  • Test, both functionality and volume, to ensure that the project deliverables meet the customer requirements and expectations.
  • Transition to operations—Once the acceptance testing has been completed, the infrastructure transitions to maintenance. This may be in-house or outsourced.

Step 4: Business Process Integration

Once the project is completed and the IoT environment is generating a data stream and providing control capabilities, the next step is to integrate the IoT system into the business. This could be simply training business unit staff on the system capabilities. In other cases, the IoT data feeds will need to be integrated with business system databases, and the ability to control processes integrated with business systems. Identity management that provides access control to data and devices will be paramount.



Support MC Press Online





  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!


  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.


  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.


  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails


  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.



  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.