Introduction In this blogpost I’ll go through the journey I went when I was setting up monitoring with ELK for my website. The task seemed simple - install *beats and tell it to report to my elk stack vm. You’ll see why in my setup it wasn’t as easy as it sounds initially. The issue If you recall my network setup had a little issue - I do not own the public IP address where my infrastructure sits.
Intro As the tittle suggests It’s time to go down infrastructure lane. In this blog post I’ll show my “home” lab and all the services I’ve built so far. I will do my best to keep this up to date so check this post regularly for updates, both to the content and the image at the end. If you are interested in just the network topology, you can find it here Without further due let’s get started.
Intro Recently I’ve been quite busy. I was helping with the organisation of HackConf this weekend which was both awesome and exhausting. Therefore this blog will be covering something simpler - how I created this site. I won’t cover the ceation of the actual ui - it is a statically generated website from markdown files (you can find the sources here). Just google for a static site generator and you’ll find plenty.
Brief intro Recently I’ve been messing around with various client-side web attacks. I’ve noticed that most web devs’ knowledge goes as far as the framework their using requires and that’s it. When asked what is the purpose of a csrf token, they would say - “Oh, it’s something for security and if I don’t put it, my forms don’t work so it must be there.” If you find yourself having a similar answer, keep on reading.