forked from iot-onboarding/mudmaker
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
183 lines (183 loc) · 7.68 KB
/
Copy pathindex.html
File metadata and controls
183 lines (183 loc) · 7.68 KB
1
2
3
4
<!DOCTYPE html><!-- Prism by TEMPLATED templated.co @templatedco Released for free under the Creative Commons Attribution 3.0 license (templated.co/license)--><html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <title>Welcome to MUD Maker</title> <meta name="viewport" content="width=device-width, initial-scale=1"> <!--[if lte IE 8]><script src="assets/js/ie/html5shiv.js"></script><![endif]--> <link rel="stylesheet" href="assets/css/main.css"> <!--[if lte IE 9]><link rel="stylesheet" href="assets/css/ie9.css" /><![endif]--> </head> <body> <!-- Banner --> <section id="banner"> <div class="inner split"> <section> <h2>Welcome to MUD Maker</h2> <br> </section> <section> <p>A tool to build your own MUD files</p> <ul class="actions"> <li><a href="mudmaker.html" class="button special">Go Right to MUD Maker</a></li> </ul> <p>A tool to visualize your MUD files</p> <ul class="actions"> <li><a href="mudvisualizer.php" class="button special">Go Right to MUD Visualizer </a></li> </ul> </section> </div> </section> <!-- One --> <section id="one" class="wrapper"> <div class="inner split"> <section> <h2>What is MUD?</h2> <p>MUD stands for Manufacturer Usage Descriptions, a standard manufacturers can use to describe what sort of network access their devices need.</p> <ul class="actions"> <li><a href="#two" class="button alt"><span style="color: #777777;">How
to<br> </span></a></li> </ul> </section> <section> <ul class="checklist"> <li>MUD provides customers information they can use to understand how devices access the network.</li> <li> MUD optionally uses existing device mechanisms to communicate those needs to the network.</li> <li> MUD can be used to keep your devices safe from other compromised devices on the network.</li> <li> MUD is an open standard. Anyone can implement it.</li> </ul> </section> </div> </section> <!-- Two --> <section id="two" class="wrapper style2 alt"> <div class="inner"> <div class="spotlight"> <div class="image"> <img src="images/therm.jpg" alt="Thermostat"></div> <div class="content"> <h3>Knowing your device</h3> The first step is documenting what access your device needs. At a minimum, this means knowing which UDP and TCP ports a device will use. MUD provides manufacturers a way to specify network access policies for devices without having to know what every customer deployment topology is. Also, don't worry about DNS or NTP, as you get those services by default.<br> <p></p> </div> </div> <div class="spotlight"> <div class="image"> <img src="images/MUDmaker.png" alt="MUD Maker Tool"> </div> <div class="content"> <h3>Building your MUD file</h3> <p>Each MUD file contains access control lists that use various classes. When you click on the checkboxes in MUD maker, additional information will appear below that you will need to fill out. Just choose which classes are appropriate for your devices. If you need more entries per class, hit the + button.</p> <ul class="actions"> <li><a href="classes.html" class="button alt">More on MUD ACLs</a> <a href="examples.html" class="button alt">Example MUD files</a></li> <li> <a href="mudmaker.html" class="button alt">Make a MUD file</a> <a href="/mudrest/mudpp" class="button alt">Pretty Print a MUD file</a></li> </ul> </div> </div> <div class="spotlight"> <div class="image"> <img src="sig.jpg" alt="MUD signature" style="width: 186px; height: 114px;"> </div> <div class="content"> Once you've built your MUD file, you should sign it. <ul class="actions"> <li><a href="signing.html" class="button alt">Details</a></li> </ul> </div> </div> <div class="spotlight"> <div class="image"> <img src="images/mud-architecture.png" alt="MUD architecture"> </div> <div class="content"> <h3>Pointing to the MUD file with a URL</h3> <p>Once you've developed your MUD file, plop it on a server somewhere. Then have your device announce a URL pointing to that file. This can be done with LLDP, DHCP, or in a certificate.</p> <ul class="actions"> <li><a href="mudurl.html" class="button alt">Details</a></li> </ul> </div> </div> <div class="inner"> <div class="spotlight"> <div class="image"> <img src="images/mudnet.png" alt="MUD Protected Network"></div> <div class="content"> <h3>Trying it out with a MUD Manager</h3> Once you have created a MUD file and a MUD URL, you can test it out. Here are a few MUD managers to try: <br> <br> <ul class="checklist"> <li> <a href="https://osmud.org">osmud.org</a> consumer open source with OpenWRT.</li> <li><a href="https://github.com/usnistgov/nist-mud">NIST MUD Manager based on OpenFlow<br> </a></li> <li><a href="https://github.com/CiscoDevNet/MUD-Manager">Cisco Radius-based proof of concept</a></li> <li><a href="https://github.com/CIRALabs/Secure-IoT-Home-Gateway">CIRA
Labs IoT Home Gateway</a></li> </ul> </div> </div> </div> </div> </section> <!-- Contact --> <section id="contact" class="wrapper"> <div class="inner split"> <section> <ul class="contact"> <li class="fa-envelope"><a href="mailto:mud@ietf.org">mud@ietf.org</a></li> </ul> <img src="images/mud.jpg" alt="MUD" style="width: 350px; height: 146px;"> <ul class="contact"> </ul> </section> <section> <h3>The Standard</h3> <a href="https://www.rfc-editor.org/info/rfc8520">RFC 8520 - Manufacturer Usage Descriptions</a><br> <br> <h3> Thanks for the artwork </h3> <tiny><a href="https://commons.wikimedia.org/w/index.php?curid=6267845">Bouchecl
- Own work, CC BY-SA 3.0</a><br> <br> </tiny> <h3>Tooling by Eliot Lear and Vafa Andalibi</h3> </section> </div> </section> <!-- Footer --> <footer id="footer"> <div class="copyright"> © Untitled. All rights reserved. Images: <a href="http://unsplash.com">Unsplash</a>. Design: <a href="http://templated.co">TEMPLATED</a>. </div> </footer> <!-- Scripts --> <script src="assets/js/jquery.min.js"></script> <script src="assets/js/skel.min.js"></script> <script src="assets/js/util.js"></script> <!--[if lte IE 8]><script src="assets/js/ie/respond.min.js"></script><![endif]--> <script src="assets/js/main.js"></script> </body></html>