#Tag
langsam füllt sich der saal 4600 im paul-löbe-haus. die #nis2-anhörung im #bundestag startet. alles stellungsnahmen (u. a. von @egouvernante @kenji @z_edian ) -> https://www.bundestag.de/ausschuesse/inneres/anhoerungen/1113440-1113440
Die "Anhörung zur NIS-2-Richtlinie" (BT-Drucksache 21/1501) im Innenausschuss des Bundestags startet um 15 Uhr und wird live übertragen.
Die überarbeitete Stellungnahme der @AG_KRITIS ist da bereits Online einsehbar.
https://www.bundestag.de/ausschuesse/inneres/anhoerungen/1113440-1113440
langsam füllt sich der saal 4600 im paul-löbe-haus. die #nis2-anhörung im #bundestag startet. alles stellungsnahmen (u. a. von @egouvernante @kenji @z_edian ) -> https://www.bundestag.de/ausschuesse/inneres/anhoerungen/1113440-1113440
Die "Anhörung zur NIS-2-Richtlinie" (BT-Drucksache 21/1501) im Innenausschuss des Bundestags startet um 15 Uhr und wird live übertragen.
Die überarbeitete Stellungnahme der @AG_KRITIS ist da bereits Online einsehbar.
https://www.bundestag.de/ausschuesse/inneres/anhoerungen/1113440-1113440
I read this article by TLD ISAC:
https://www.tld-isac.eu/guidelines-for-a-resilient-dns/
Then I found myself commenting on LinkedIn.
"Very nice article!
Thanks for mentioning NLnet Labs NSD as one of the trusted name servers, along with Internet Systems Consortium, CZ.NIC, z.s.p.o. and PowerDNS. What surprises me is that with regards to resilience of these software solutions, the article just says to "run updates" to be prepared for vulnerabilities.
DNS service providers and TLD registries are ‘sectors of high criticality’ under the European #NIS2 directive. On the NIS2 supply chain security requirements, ENISA guidance says: “Ensure that support contracts cover the system life cycle and obsolescence management requirements, including the date until which the system must be supported”.
Thus, what would be a better recommendation is to have a support agreement with an SLA in place with one of these parties. This way, you get notifiied of vulnerabilies under NDA before they become public. At the same time, the agreement keeps the work of the #OpenSource software developer sustainable.
After all, when you purchase an HSM to keep your DNSSEC keys safe, budgeting to have a support agreement with the supplier in place is a no-brainer, so why not with the party who provides your critical #DNS name server software?”
I read this article by TLD ISAC:
https://www.tld-isac.eu/guidelines-for-a-resilient-dns/
Then I found myself commenting on LinkedIn.
"Very nice article!
Thanks for mentioning NLnet Labs NSD as one of the trusted name servers, along with Internet Systems Consortium, CZ.NIC, z.s.p.o. and PowerDNS. What surprises me is that with regards to resilience of these software solutions, the article just says to "run updates" to be prepared for vulnerabilities.
DNS service providers and TLD registries are ‘sectors of high criticality’ under the European #NIS2 directive. On the NIS2 supply chain security requirements, ENISA guidance says: “Ensure that support contracts cover the system life cycle and obsolescence management requirements, including the date until which the system must be supported”.
Thus, what would be a better recommendation is to have a support agreement with an SLA in place with one of these parties. This way, you get notifiied of vulnerabilies under NDA before they become public. At the same time, the agreement keeps the work of the #OpenSource software developer sustainable.
After all, when you purchase an HSM to keep your DNSSEC keys safe, budgeting to have a support agreement with the supplier in place is a no-brainer, so why not with the party who provides your critical #DNS name server software?”
Mehrere Quellen haben es bestätigt:
#NIS2 ist morgen im Bundeskabinett!
Der unbestimmte § 28 Absatz 3 mit den "vernachlässigbaren Tätigkeiten" ist wohl drin geblieben. Das wird ein sehr interessantes parlamentarisches Verfahren!
Das Gesetz geht danach, wenn alles klappt, am 26.9. in den Bundesrat zum Plenar-Termin und dann an den Bundestag zur 1. Lesung.
Und offenbar wurden die Bundesministerien fast alle wieder raus genommen, weil kostet ja Geld... 🤷♀️
https://de.m.wikipedia.org/wiki/NIS-2-Richtlinie
Mehrere Quellen haben es bestätigt:
#NIS2 ist morgen im Bundeskabinett!
Der unbestimmte § 28 Absatz 3 mit den "vernachlässigbaren Tätigkeiten" ist wohl drin geblieben. Das wird ein sehr interessantes parlamentarisches Verfahren!
Das Gesetz geht danach, wenn alles klappt, am 26.9. in den Bundesrat zum Plenar-Termin und dann an den Bundestag zur 1. Lesung.
Und offenbar wurden die Bundesministerien fast alle wieder raus genommen, weil kostet ja Geld... 🤷♀️
https://de.m.wikipedia.org/wiki/NIS-2-Richtlinie
RFC erratum https://www.rfc-editor.org/errata/eid8305 is interesting because it is an example of the free-form (natural language) and formal schema in a #RFC saying different things.
Thanks TechRadar for the review:
‘Soverin is a simple and solid secure email service that does a good job of protecting your data and privacy.”
Soverin is designed for the new reality:
No ads, no tracking, no data mining, no lock-in
Hosted in the Netherlands, fully under EU jurisdiction
Bring your own domain and stay in control
Read the full review: https://www.techradar.com/pro/software-services/soverin-secure-email-review
#DigitalSovereignty #NIS2#GDPR#ISO27001#SecureEmail #PrivacyByDesign
Thanks TechRadar for the review:
‘Soverin is a simple and solid secure email service that does a good job of protecting your data and privacy.”
Soverin is designed for the new reality:
No ads, no tracking, no data mining, no lock-in
Hosted in the Netherlands, fully under EU jurisdiction
Bring your own domain and stay in control
Read the full review: https://www.techradar.com/pro/software-services/soverin-secure-email-review
#DigitalSovereignty #NIS2#GDPR#ISO27001#SecureEmail #PrivacyByDesign
ENISA published guidance on the #NIS2 implementing act for the digital sector. They cover how to apply the NIS2 requirements when it comes to #FOSS, including clarifying that in most cases upstream open source maintainers should not be considered a ‘direct supplier’. There are 37 occurrences of #opensource in the text. Some quotes to follow https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance
ENISA published guidance on the #NIS2 implementing act for the digital sector. They cover how to apply the NIS2 requirements when it comes to #FOSS, including clarifying that in most cases upstream open source maintainers should not be considered a ‘direct supplier’. There are 37 occurrences of #opensource in the text. Some quotes to follow https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance
A space for Bonfire maintainers and contributors to communicate
