MariaDB Versus MySQL

https://seravo.fi/2015/10-reasons-to-migrate-to-mariadb-if-still-using-mysql

https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features

For the most part we run our database servers using Maria DB on Debian 8, we opt to access them using an external editor or access via command line. As many in the industry will tell you, sometimes running phpmyadmin and other php based utilities server-side on database servers in a production environment can leave you inevitability vulnerable to exploits.

Enforcing HTTPS and locking down the .htaccess file can help, but many suggest you choose to leave your MariaDB/MySQL server not running a web-server back end on top and administrating your database(s) with either command line or management programs that can connect remotely.

There’s industry best practice, there’s your best practice and then there’s questionable practice.
Just because it’s easy and convenient, doesn’t mean you won’t risk compromising sensitive information. You have an ethical obligation to do what is in the best interests of your users, your customers, your administrators and the rest of us the look to you to set a high standard by which we should try to maintain.

Security issues with WPS (Wireless Protected Setup)

It’s actually one of the first thing we often disable, WPS, UPnP, use WPA-PSK2 with AES. MAC addressing and if you feel the need use RADIUS.
Just because it’s easy, that doesn’t mean it’s a good idea.

https://nakedsecurity.sophos.com/2014/09/02/using-wps-may-be-even-more-dangerous/
http://www.howtogeek.com/176124/wi-fi-protected-setup-wps-is-insecure-heres-why-you-should-disable-it/

http://www.computerworld.com/article/2476114/network-security/the-woops-of-wps–wi-fi-protected-setup–raises-its-ugly-head-again.html