koa-protect v1.0.1

Koa-Protect by Altonotch

Works on Node.js v7 and newer.

The purpose of this module is to provide out-of-box, proactive protection for common security problems, like
SQL injection attacks, XSS attacks, brute force, etc...

This module is not a silver bullet, and is not a substitute for security-minded engineering work. But it can help you to achieve your goals.

Basic usage

npm i koa-protect --save

With Express

const protect = require('koa-protect')
const Koa = require('koa')  
const bodyParser = require('koa-bodyparser')
const redis = require('redis')
const client = redis.createClient()  
  
const app = new Koa()
  
app.use(bodyParser.json())  

const router = require('koa-router')()
  
app.use(protect.koa.sqlInjection({  
    body: true,  
    loggerFunction: console.error  
}))  
  
app.use(protect.koa.xss({  
    body: true,  
    loggerFunction: console.error  
}))  
  
app.use(ratelimit({  
    db: client,  
    duration: 60000,  
    errorMessage: 'Sometimes You Just Have to Slow Down.',  
    id: (ctx) => ctx.ip,  
    headers: {  
        remaining: 'Rate-Limit-Remaining',  
        reset: 'Rate-Limit-Reset',  
        total: 'Rate-Limit-Total'  
    },  
    max: 100  
}));  
  
app.use(router.routes())  
app.use(router.allowedMethods());  
  
app.listen(process.env.PORT || 3000, (err) => {  
    if (err) {  
        return console.error('server could not start')  
    }  
    console.log('server is running')  
})  

API

protect.koa.sqlInjection([options])

Returns an Koa middleware, which checks for SQL injections.

• options.body: if this options is set (true), the middleware will check for request bodies as well
  • default: false
  • prerequisite: you must have the body-parser module used before adding the protect middleware

• options.loggerFunction: you can provide a logger function for the middleware to log attacks

  • default: noop

protect.koa.xss([options])

Returns an Koa middleware, which checks for XSS attacks.

• options.body: if this options is set (true), the middleware will check for request bodies
  • default: false
  • prerequisite: you must have the body-parser module used before adding the protect middleware

• options.loggerFunction: you can provide a logger function for the middleware to log attacks

  • default: noop

** The example app is making use of koa ratelimit module (https://github.com/koajs/ratelimit)

ratelimit([options])

• db redis connection instance
• duration of limit in milliseconds 3600000
• errorMessage custom error message
• id id to compare requests ip
• headers custom header names
• max max requests within duration 2500
• remaining remaining number of requests 'X-RateLimit-Remaining'
• reset reset timestamp 'X-RateLimit-Reset'
• total total number of requests 'X-RateLimit-Limit'

protect.koa.headers([options])

The headers object is a reference to the main helmet object exported.
For docs on the options object, please refer to the helmet documentation.

Security Recommendations

As mentioned, this module isn't a silver bullet to solve your security issues completely. The following information is provided to hopefully point you in the right direction for solving other security concerns or alternatives that may be useful based on your budget or scale.

Other Aspects

There are plenty of other areas that you should be concerned about when it comes to security, that this module doesn't cover (yet or won't) for various reasons. Here are a few that are worth researching:

• Password Hashing
  • Bcrypt modules: bcrypt,bcryptjs, bcrypt-as-promised
  • Scrypt modules: scrypt, scryptsy, scrypt-async
• NoSQL Injection
• Session management
• CSRF - Cross Site Request Forgery
  • CSURF Express Module

• Signed Cookies: cookie-parser Express Module

Resources

• OWASP -Open Web Application Security Project
• Express: Production Best Practices

• RisingStack: Node.js Security Checklist

Dedicated WAF

If you have the resources available (budget or hosting environment), a dedicated WAF (Web Application Firewall) can offer a robust solution to various security issues, such as blocking potential attackers and flagging their activity.

• OWASP WAF information
• Hosting providers:
  • AWS WAF
  • Microsoft Azure WAF
• ModSecurity - Apache, nginX and other web servers.
• CloudFlare - External WAF features.