The simplicity of secure HIP-based networking offers relief for IT teams struggling to meet the demands of business units.\u00a0\nThe demands for business agility and tighter security are in conflict. The first requires quick and responsive implementation of whatever is needed to take advantage of business opportunity. But that runs headlong into the management of network access and security policies. Automation and orchestration are the keys to overcoming this conflict, but the inherent flaws of IP networking are the fly in the ointment.\nIt\u2019s no surprise that businesses are overwhelmed by the challenge of cyber security. In the 2017 Network World State of the Network report, protecting against data breaches and leaks was the top challenge cited by both enterprise and small to medium-sized business (SMB) IT decision makers. Part of the problem lies with lack of automation to augment understaffed Security Operations Centers (SOCs).\n\u201cUnderstaffed and under-skilled SOC teams depend on key individuals and manual processes to get their jobs done,\u201d ESG\u2019s Jon Oltsik writes in a column for CSO Online. \u201cAnd when cyber security professionals detect something wrong, they don\u2019t work well with the IT operations team to fix problems in an efficient manner.\u201d\u00a0\nNobody foresaw this\nAnother part of the problem is that IP addressing is being used to an extent that is magnitudes beyond what its inventors intended. As a Washington Post feature story on the \u201cnet of insecurity\u201d points out, the internet\u2019s founders \u201csaw its promise but didn\u2019t foresee users attacking one another.\u201d\nBy implementing the TCP\/IP protocol to make it easy to find computer devices, it became easy for malicious users to attack devices\u2014they could use IP addressing not only to locate and identify another device, but also to spoof their own addresses to make it difficult to deflect an attack.\nMoreover, as industry analyst Zeus Kerravala writes in Network World, \u201cSince it\u2019s impossible to give every device its own unique IP address, the clever folks at networking companies came up with an assortment of workarounds, such as being able to NAT (network address translation) non-routable, private addresses. And as we\u2019ve added more dynamic environments, such as private and public cloud, defining policy based on addresses or ranges has become unsustainable.\u201d\u00a0\nIn 2015, a new addressing standard was ratified by the IETF as an open networking security protocol aimed at overcoming the flaw of TCP\/IP addressing. \u201cThe Host Identity Protocol (HIP) provides a method of separating the end-point identifier and locator roles of IP addresses,\u201d according to the IETF HIP working group. \u201cIt introduces a new Host Identity (HI) namespace, based on public keys, from which endpoint identifiers are taken. The public keys are typically, but not necessarily, self-generated. HIP uses existing IP addressing and forwarding for locators and packet delivery.\u201d\nCreating secure network overlays\nImplemented commercially with Tempered Networks\u2019 Identity-Defined Networking (IDN) products and services, HIP makes it possible to easily create secure network overlays based on cryptographic namespace identities.\nThe Tempered Networks Conductor, a policy management and orchestration engine, makes it possible to create hub-and-spoke or highly distributed mesh networks without the traditional network challenges. As a result, end-to-end or peer-to-peer encrypted networking is now possible and can be done in as little as three steps, even for traditionally non-routable endpoints.\nThe simplicity of secure HIP-based networking offers relief for overburdened IT teams struggling to meet the demands of business units. For more information, download this white paper on the Identity-Defined Network architecture.