metlo VS helmet

So far, I’ve been using Metlo's protection features to initially test out its capabilities on my app, but there’s still a whole other Testing feature that it has that I'm starting to look into. Everything I’ve tried out has been pretty quick and easy so hopefully I can play around with the Testing more to help me catch any other authentication or authorization vulnerabilities that might exist in my app. If this is something that interests you, you can check it out at https://metlo.com .

* Once you have the right templates you can build rules to apply these templates to many endpoints at once (https://docs.metlo.com/docs/test-rules). This makes it possible to write hundreds of tests against your API in just a few clicks :)

We have more info on our docs here: https://docs.metlo.com/docs/writing-a-test. And here's a demo video if you’d like a quick walk-through :) https://www.loom.com/share/f342f186e756489aa7a500be875a5539

We’d love to hear your thoughts!

[0] https://github.com/metlo-labs/metlo

Our website is at https://metlo.com, repo is at https://github.com/metlo-labs/metlo. There’s a demo video here: https://www.loom.com/share/2c38c731cf044288995e5ee2566528a7. Check out our sandbox at https://demo.metlo.com (no email required). You can get started with our hosted service (in Beta) for free at https://app.metlo.com/signup (there’s an always free tier, and paid tier is not enforced yet) , or you can self-host by following the instructions at https://docs.metlo.com/docs/deploy-to-aws.

helmet

By default, NuxtSecurity will set security response headers to match the values recommended by OWASP and a popular Express.js middleware called helmet.

Utilize security headers and middleware to add another layer of security to your Node.js application. Tools like Helmet.js can help you set secure HTTP headers, while middleware can assist in filtering and sanitizing user inputs.

Documentation Link: helmet

Helmet helps “sanitise” the input, which might not have come from the UI directly. Mongoose is what is known as an Object Document Modelling (ODM), which defines a structure (schema) for the stored data, making it easier to manage in Express. These additions have been omitted from our example stack purely to simplify the tutorial and focus on the fundamental tiers and interfaces.

If you can repro the issue with a minimal tsconfig, with nothing but an import statement then it's probably something the maintainers of helmet would like to see. There's also this (recent) issue I saw looking at their queue -- maybe related? https://github.com/helmetjs/helmet/issues/424 ...

// Security // https://helmetjs.github.io/ app.use(helmet())

You can learn more about each header and how to configure them in the Helmet documentation.

These days I only use middleware if it's global and has no outputs. Helmet comes to mind.