shotting.cc

DEFCON-1

HOME

WELCOME TO SHOTTING.CC

Welcome to the IoT Security Lab 101

In this whitepaper on IoT Security, we touch on detailed analysis of design patterns implimented in the IoT Security Paradigm.

Security Checklist

We have a reversed engineer'ed example of user interaction - being - they store data. Lots of data. Not only data - but their LIVES, on IoT devices. This is why a data breach on such an account might have suicidal impacts - hence the desperate demand for super level security on such devices. Not only for C-Class Employees, or even www.1.com NEO level security, but for the poor black child in Africa too.

1. DESIGN PATTERN #1 : CONTAINER

THE CONTAINER OBJECT MUST HAVE INNATE SECURITY. SUCH AS A SELF-EXTRACTING ZIP, THIS DATA CONTAINER REQUIRES A SOFTWARE CONSTRUCTED ENVRIONMENT TO SELF-EXTRACT IN A SECURE FASHION - OFTEN USING USER INTERACTION AS THE AUTHENTICATION MECHANISM.

2. DESIGN PATTERN #2 : SELECTION

BUILDING YOUR OWN SECURITY DEFENCES BY SELECTING FROM AN UNISEQ INDEXXED LIST OF TOP USER CHOICES FOR POSSIBLE SECURITY CONFIGURATIONS FOR YOUR DEVICE FROM, PARANODE, TO WILD WEST.

SECURITY BY CHOICE. JUST AS METASPLOIT HAS A MYRIAD OF EXPLOITS ON CHOICE , THE SECURITY TEAM ARE REQ. TO BUILD SECURITY SELECTION BOXES INTO EXISTING IOT DEVICES.

3. DESIGN PATTERN #3 : NODE

WHAT IS A NODE? A TOP LEVEL DOMAIN TERM OF A SECURITY CONCEPT. A NODE HAS A CONTAINER FOR THE USER, AUTHENICATIONS, AND INTERFACES. IT IS NOT THE GUI, BUT A LAYER TRANSPOSED FROM THE GUI. IN EVERY SYSTEM THE APPLICATION GIVES AWAY A VARIETY OF TOPICAL INFORMATION. ESPECIALLY IN WINDOWS TEN, THE INTERNALS ARE GETTING BIGGER THAN THE USER LEVEL.

THEREFORE, AN APPLICATION MUST BE DESIGNED FROM BOTTOM UP TO USE SECURITY IN OBSCURITY. FOR INSTANCE, HAVING AN ENCRYPTED USER LAND FROM THE SYSTEM BOOT STRAP IS ESSENTIAL.

IN CONCLUSION, NODES THAT HAVE CONTAINERS MUST SPEAK IN FORKED TONGUES FOR APACHE INDIAN RULE COMMUNICATIONS SYSTEMS.