The second OSS standard

Secure ID – Simple. Good..

What’s special about it is that it’s so simple. So simple and so safe that it raises the question: why hasn’t it existed for a long time? Counter question: Why don’t all car rims have the same five holes? The simple answer: If they had, then after selling their old car, the owner could keep the winter rims and reuse them on the new vehicle. Since this standard does not exist, the customer will in all likelihood have to buy new rims. It doesn’t make economic sense, at least not from the customer’s point of view.

The OSS stays out of the production of car rims. Instead, we write standards for credentials that grant access rights. However, the principle is the same. However, our standard is about how to put an ID number on an ID card. As we do, end customers benefit from the fact that they do not have to have their ID cards adjusted again if they change suppliers. That saves costs.

In addition to the cost argument, security speaks for the new, second OSS standard. Our first standard was an application that read AND wrote data. IT security experts gave us the idea of separating the two for more security.

For those who want maximum security, we have found a way to separate reading and writing of data with the Secure ID by Oss standard . The new application first reads the card number from the SID and only then accesses the standard offline application. In this way, there is maximum certainty that the correct ID number has been read…

Of course, the secure ID number can also be used for other applications such as secure copying, time recording, parking, key management, etc.