It is that time of the year again folks! APRICOT 2015 has started and as usual it is jam-packed with interesting workshops, tutorials and talks. If you haven’t seen the program, I suggest that you have a peek at it now. Even if you are not able to be here physically in beautiful Fukuoka, you can still attend the sessions remotely. Technology is awesome!
Just like in APRICOT 2014 and APNIC 38, we are continuing the collaboration with APCERT to organize the security related sessions. There will be four sessions in total on Day 9 of APRICOT2015 (that is Wednesday, March 4th 2015) and we will have about 11 presenters sharing about the threat landscape in the region, lessons learned, best-practices and highlights of relevant initiatives. There is a mix bag of presenters from the national CERTs like JPCERT, CERT-AU, CNCERT, KRCERT and MYCERT (to name a few) as well as from the industry such as Team-Cymru, Dell SecureWorks, NTT-CERT and ISOC.
I think there’s great opportunities for attendees – especially APNIC Members – to learn about recent security issues or initiatives in the region. But beyond that, the chance to network and exchange ideas on how security incidents or abuses could be handled or coordinated more effectively. We know that there is definitely room for improvements for the abuse contacts or IRT objects in the Whois database.
Here is a quick video of me and Arnold Yoon talking about CERTs and network operator coordination.
I should also mention that right after APCERT Session 4, there will be a Messaging, Malware and Mobile Anti Abuse Working Group (M3AAWG) BoF that is also worthwhile checking out.
On top of that, I am also aware that my APCERT colleagues will have their steering committee meeting next week and will be joined by friends from the OIC-CERT as they are planning for the first APCERT – OIC-CERT joint conference in September 2015 in Kuala Lumpur, Malaysia. I wish them a successful meeting.
So I look forward do seeing everyone at the APRICOT2015 & APCERT Security Sessions!
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.