<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz" -->

---
title: Beskar 0.2.0 - Rails Security Engine | daily.dev
description: Beskar 0.2.0, an open-source Rails security engine for Rails 8+, adds database-coordinated authentication rate limits, durable session revocation, and...
canonical: https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Beskar 0.2.0 - Rails Security Engine | daily.dev
og:description: Beskar 0.2.0, an open-source Rails security engine for Rails 8+, adds database-coordinated authentication rate limits, durable session revocation, and...
og:url: https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz
og:image: https://api.daily.dev/og/posts/RU6W3VTrZ.png
og:image:alt: Beskar 0.2.0 - Rails Security Engine
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Beskar 0.2.0 - Rails Security Engine

**[Ruby Flow](https://daily.dev/sources/rubyflow)** · 7 min read · 0 upvotes · 0 comments

## Summary

Beskar 0.2.0, an open-source Rails security engine for Rails 8+, adds database-coordinated authentication rate limits, durable session revocation, and auditable administration for apps using Devise or Rails' built-in authentication. Features include IP/account admission windows enforced via the database (no Redis required), account locking that invalidates sessions including Devise remember-me credentials, scanner detection with escalating IP bans, a security dashboard with permissioned CSV/JSON export, and required operator identity tracking for administrative actions. Upgrading from 0.1.0 requires running new migrations, updating authentication hooks and initializer configuration, coordinating worker restarts, and planning a one-time Devise sign-out since old cache counters are not imported. The release is MIT licensed and built by AuditBadger.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://auditbadger.com/beskar>

## Questions this post answers

### How do I upgrade Beskar from 0.1.0 to 0.2.0 in a Rails app?

Upgrading requires running the new migration generator (bin/rails beskar:install:migrations) and bin/rails db:migrate before starting upgraded workers, then updating authentication hooks and dashboard permissions in the initializer, draining old workers, and coordinating restarts. A one-time Devise sign-out should be planned since old cache counters are not imported, and legacy bans from observation-mode versions should be reviewed.

_Rails teams tracking breaking changes before an upgrade can follow release details like this on daily.dev._

### Does Beskar require Redis for Rails authentication rate limiting?

No, Beskar coordinates IP and account admission limits through the database rather than requiring Redis or another shared cache. The database is authoritative for every ban decision across workers and restarts, and enforcement does not depend on Rails.cache, so stale cache entries never decide whether a request is blocked.

_Comparing auth rate-limiting approaches for Rails apps is easier with releases like this tracked on daily.dev._

### Does locking a user account in Beskar invalidate existing Devise sessions?

Yes, supported account locks invalidate existing sessions, including Devise remember-me credentials, and unlocking does not restore the old credentials. Rails-native applications (non-Devise) must integrate Beskar's session guards separately to get equivalent revocation behavior.

_Developers hardening Devise-based authentication can follow security engine updates like this on daily.dev._

## Similar posts on daily.dev

- [Rails Security Best Practices: A Comprehensive Guide](https://daily.dev/posts/rails-security-best-practices-a-comprehensive-guide-4klfoqpgy) · Saeloun · 0 upvotes · 0 comments
- [Rails 8 Built-in Auth vs. Devise: Why the Default Finally Wins](https://daily.dev/posts/rails-8-built-in-auth-vs-devise-why-the-default-finally-wins-avm1gdila) · Ruby Flow · 0 upvotes · 0 comments
- [Rails 8 Authentication: Why the New Built-in Generator Matters \(and What It Means for Devise\)](https://daily.dev/posts/rails-8-authentication-why-the-new-built-in-generator-matters-and-what-it-means-for-devise--t3hvupk92) · Ruby Flow · 0 upvotes · 0 comments

---

Tags: [#open-source](https://daily.dev/tags/open-source), [#authentication](https://daily.dev/tags/authentication), [#rails](https://daily.dev/tags/rails)

[View this post on daily.dev](https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Beskar 0.2.0 - Rails Security Engine","url":"https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz"},"datePublished":"2026-09-21T16:57:53.304Z","dateModified":"2026-09-21T16:58:16.651Z","description":"Beskar 0.2.0, an open-source Rails security engine for Rails 8+, adds database-coordinated authentication rate limits, durable session revocation, and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2359883dce99ce7f0544e62cb4325c3f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2359883dce99ce7f0544e62cb4325c3f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Ruby Flow","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Ruby Flow","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/a21aaa8bcbbf448193a016895c90a0e1","url":"https://daily.dev/sources/rubyflow"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,authentication,rails","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Ruby Flow","item":"https://daily.dev/sources/rubyflow"},{"@type":"ListItem","position":3,"name":"Beskar 0.2.0 - Rails Security Engine"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/beskar-0-2-0---rails-security-engine-ru6w3vtrz#faq","mainEntity":[{"@type":"Question","name":"How do I upgrade Beskar from 0.1.0 to 0.2.0 in a Rails app?","acceptedAnswer":{"@type":"Answer","text":"Upgrading requires running the new migration generator (bin/rails beskar:install:migrations) and bin/rails db:migrate before starting upgraded workers, then updating authentication hooks and dashboard permissions in the initializer, draining old workers, and coordinating restarts. A one-time Devise sign-out should be planned since old cache counters are not imported, and legacy bans from observation-mode versions should be reviewed. Rails teams tracking breaking changes before an upgrade can follow release details like this on daily.dev."}},{"@type":"Question","name":"Does Beskar require Redis for Rails authentication rate limiting?","acceptedAnswer":{"@type":"Answer","text":"No, Beskar coordinates IP and account admission limits through the database rather than requiring Redis or another shared cache. The database is authoritative for every ban decision across workers and restarts, and enforcement does not depend on Rails.cache, so stale cache entries never decide whether a request is blocked. Comparing auth rate-limiting approaches for Rails apps is easier with releases like this tracked on daily.dev."}},{"@type":"Question","name":"Does locking a user account in Beskar invalidate existing Devise sessions?","acceptedAnswer":{"@type":"Answer","text":"Yes, supported account locks invalidate existing sessions, including Devise remember-me credentials, and unlocking does not restore the old credentials. Rails-native applications (non-Devise) must integrate Beskar's session guards separately to get equivalent revocation behavior. Developers hardening Devise-based authentication can follow security engine updates like this on daily.dev."}}]}
```

