With IoT, 5G and embedded devices becoming a larger part of everyone’s daily lives, security—and more importantly, trust in our technology—is on everyone’s minds. Embedded devices don’t have a good security track record; the last several years saw a significant number of high-profile hacks that could prevent people from widely accepting IoT into their homes. . The proliferation of hacks and the threat to basic infrastructure resulted in a move toward regulating the security of critical software. Specifically, Executive Order 14082, issued by United States, drew up a list of security practices, including the inclusion of a software bill of materials (SBOM), with every application run by the U.S. federal government. The National Institute of Standards and Technology (NIST) is also creating reference architectures and templates for application security as a result of the Executive Order. Regulation is coming to software security that will likely impact every company that produces code or sells products running on code. Check out these six tips on protecting your IoT devices from hackers. . Surge in cyber attacks drives regulatory changes in safeguarding embedded systems and IoT device security initiatives.. Embedded Security, IoT Trust, Application Regulation, Cybersecurity Best Practices. . Brittany Day
In this article we continue our discussion of some of the foundations of public key infrastructure (PKI) that we began in an earlier article, where we discussed the role of keys, certificates, and trust. While discussing the importance of distributed (or transitive) trust in PKI design, we outlined the job of the certificate authority (CA) in PKI, giving the general idea of its role in certificate issuance and management. Here, we'll explore the how and when one might wish to establish one's own CA when incorporating a PKI into an enterprise design. . . .. In this article we continue our discussion of some of the foundations of public key infrastructure (PKI) that we began in an earlier article, where we discussed the role of keys, certificates, and trust. While discussing the importance of distributed (or transitive) trust in PKI design, we outlined the job of the certificate authority (CA) in PKI, giving the general idea of its role in certificate issuance and management. Here, we'll explore the how and when one might wish to establish one's own CA when incorporating a PKI into an enterprise design. We'll expand the discussion of CA implementation and use by giving practical examples using two widely available tools, OpenSSL and keytool. Bear in mind that many of the topics that we'll touch on require a deeper background than is practical to present within the scope if this article. Where applicable, we'll provide pointers to useful references. Why do I need a CA? As discussed in our earlier article, the CA is a crucial component of any PKI, as it provides public-key certificate issuance, management, and revocation services to PKI users, thus enabling distributed trust relationships. In general, the CA is usually not a singular entity, but a hierarchical collection of authorities, with a root CA at the top of the structure acting as the most trusted (and most authoritative) entity in the organization. The link for this article located at newsforge.com is no longer available. . In this article wecontinue our discussion of some of the foundations of public key infrastructure (. article, continue, discussion, foundations, public, infrastructure. . Anthony Pell
Some people would have you believe this is monumental or out of the ordinary -- a group that distributes software experiencing a compromise, then letting everybody know about it and warning of the potential risks. Those that prance about in Penguin-embroidered cheerleader tops and yellow and black tutus suggest between pom-pom waves that no commercial vendor would ever be as candid.. . .. Some people would have you believe this is monumental or out of the ordinary -- a group that distributes software experiencing a compromise, then letting everybody know about it and warning of the potential risks. Those that prance about in Penguin-embroidered cheerleader tops and yellow and black tutus suggest between pom-pom waves that no commercial vendor would ever be as candid. I think that's wrong. When you get owned, somebody is going to announce it, so there's no reason for anyone -- commercial vendors included -- to try and keep it under wraps. People talk. This is our nature, and inevitably the gossip subway is going to go rumbling down the tracks, out of control, until it breaks through the surface. Moreover, open projects are in a situation that uniquely requires immediate disclosure of a compromise. A project that does not publicly admit a compromise not only risks the integrity of the project, but also risks the trust that users put in the project. And in current form, open-source projects are built entirely on trust. This trust in open-source generally springs from the practice of distributing the source code for applications. But users who download from the project can't be assured that the application hasn't been tampered with, unless they actually read through the source code. There's no guarantee that the source is actually the source that was intended. The link for this article located at is no longer available. . Open-source initiatives need to prioritize clarity and reliability even when facing challenges in program dissemination.. Open Source Integrity, Project Transparency, Community Trust. .LinuxSecurity.com Team
Noel writes about some things that a System Administrator should consider about trust when configuring or maintaining a system. "One of the first things many of us think about is the trust we give to the users of our systems. . . . . Noel writes about some things that a System Administrator should consider about trust when configuring or maintaining a system. "One of the first things many of us think about is the trust we give to the users of our systems. Some of these users have special privileges so that they can perform their own jobs." A System Administrator has a strange relationship with the equipment they manage, with the people using their system and with the world outside their systems. They have to walk a fine line between making their systems unusable and leaving them unsecured or unreliable. To make things even more complicated the line is different for each and every situation. In this article I will overview some of the choices and decisions that a System Administrator must understand and make when building or maintaining their systems. The link for this article located at Rootprompt.org is no longer available. . In IT security, System Administrators are vital for protecting systems and data. Prioritizing trust is key through account integrity, user privilege management, and security audits. Trust Management,System Configuration,User Access Control. . Anthony Pell
One of the most difficult decisions in any given enviroment is the distribution of trust. Who can you trust and with how much access? If you have a Systems Administrator on-site then they probably have super user access . . .. One of the most difficult decisions in any given enviroment is the distribution of trust. Who can you trust and with how much access? If you have a Systems Administrator on-site then they probably have super user access on at least one or more boxes within your enterprise. What about techs who occassionaly need to perform tasks that are beyond the range of their limited access? The issue of trust is a difficult one. We all spend so much time focusing our energies on unknown parties trying to get into our systems that we often forget that we need to consider what those who are already inside can do. This SunWorld article discusses some of the issues involved in dealing with internal trust decisions and what can be done to protect critical systems from internal attack. The link for this article located at SunWorld is no longer available. . Safeguarding confidence in your network is vital. Discover essential choices regarding whom to rely on and the effects of various access permissions.. Trust Management, Access Levels, Internal Security. . LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.