Architectural considerations for IoT device security in the home
Request for comments
Chose your color
Frequently visited
Frequently asked questions
The Whois is an easy-to-use tool for checking the availability of a .nl domain name. If the domain name is already taken, you can see who has registered it.
On the page looking up a domain name you will find more information about what a domain name is, how the Whois works and how the privacy of personal data is protected. Alternatively, you can go straight to look for a domain name via the Whois.
To get your domain name transferred, you need the token (unique ID number) for your domain name. Your existing registrar has the token and is obliged to give it to you within five days, if you ask for it. The procedure for changing your registrar is described on the page transferring your domain name.
To update the contact details associated with your domain name, you need to contact your registrar. Read more about updating contact details.
When a domain name is cancelled, we aren't told the reason, so we can't tell you. You'll need to ask your registrar. The advantage of quarantine is that, if a name's cancelled by mistake, you can always get it back.
One common reason is that the contract between you and your registrar says you've got to renew the registration every year. If you haven't set up automatic renewal and you don't renew manually, the registration will expire.
Wanneer je een klacht hebt over of een geschil met je registrar dan zijn er verschillende mogelijkheden om tot een oplossing te komen. Hierover lees je meer op pagina klacht over registrar. SIDN heeft geen formele klachtenprocedure voor het behandelen van een klacht over jouw registrar.
Would you like to be able to register domain names for customers or for your own organisation by dealing directly with SIDN? If so, you can become a .nl registrar. Read more about the conditions and how to apply for registrar status on the page becoming a registrar.
Request for comments
As part of our efforts to improve the security of the Internet of Things, we have been working, with a number of other experts from the RIPE community (Sandoche Balakrichenan, Eliott Lear, Jim Reid, Michael Richardson, Phil Stanhope, Peter Steinhäuser and Jan Zorz), on a draft version of the report "Architectural Considerations for IoT Device Security in the Home". The report is intended for internet service providers (ISPs). The goal of the report is to provide practical advice on currently available technologies that can be used to protect home networks, and that can be included when ISPs specify requirements for customer-provided equipment ('CPE devices').
While there are many publications about secure design principles for IoT devices themselves, there is little guidance regarding features and technologies that can be used on CPE devices to protect home networks. Our report focuses on that topic, discussing several key aspects of IoT devices, from secure deployment in home networks to the detection and mitigation of malicious activity. Topics explored include:
Securely introducing the device to the network
Seeing that it gets the access it needs (and no more)
Retrospective assessment of whether the device is behaving appropriately
Some principles device manufacturers should follow to ensure user safety and privacy
Putting it all together
We have submitted an early version of the report to the RIPE IoT Working Group, with the request that it is accepted this as a (draft) RIPE BCOP document. A decision on acceptance has not yet been made, but it will be discussed at the RIPE IoT Working Group meeting at RIPE 81. RIPE is a community where operators, manufacturers and researchers meet to discuss operational aspects of the Internet. The RIPE IoT Working Group was formed to discuss operational challenges and opportunities presented by the Internet of Things, and we believe that it is the best forum for further discussion of the report. You can find the request, as well as the draft itself, in the mailing list archives.
If you wish to see the report adopted as a Working Group document, or if you have comments about the document itself, please join the RIPE IoT Working Group mailing list and post your comments there, or join us at next week's RIPE session. The IoT Working Group meets on 29 October at 14:00 CET.
Article by:
Share this article