Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Pilcrow has released a personal handbook on authentication that serves as a free collection of guides, recommendations, and code examples for implementing secure authentication in web applications.
The book focuses primarily on authentication and authorization systems for web apps and directs readers to the OWASP Cheat Sheets series for broader security topics. It is available without cost or advertising and includes both JavaScript and Go examples hosted on GitHub.
Authentication Methods
The simplest approach uses a username and password, yet the text details multiple risks including weak or reused passwords, phishing, and database compromise. Email addresses are presented as globally unique identifiers that also enable password recovery through time-limited links or codes.
For stronger protection, the guide covers two-factor and multi-factor authentication using SMS codes or authenticator apps. It notes that these methods should be viewed as rate-limiting mechanisms rather than absolute security and advises against reusing email verification as a second factor when it is also used for password resets.
Passwordless options receive detailed treatment, including one-time codes or magic links sent via email. Passkeys based on public-key cryptography are highlighted for resistance to brute-force attacks and phishing while offering convenience through device biometrics or a master password. External hardware tokens such as YubiKey devices are discussed for both passkey support and corporate second-factor use.
The author recommends supporting both email-based and passkey authentication so users can select their preferred method, with passkeys enforced for high-security accounts.
Session Management
Because HTTP is stateless, the book explains the necessity of server-side session records paired with client tokens. Session secrets must be generated from cryptographically secure random sources, hashed with SHA-256, and combined with an identifier into a single token using encodings such as hex or base64url.
Recommended practices include setting reasonable expiration times, optionally binding sessions to geographic regions derived from IP addresses, and invalidating sessions on logout or password change. The guide stresses that session invalidation is a privileged operation and that operation-specific sessions should be used for sensitive actions such as password updates or passkey registration.
Email Addresses and Final Advice
Email addresses are endorsed as reliable account identifiers because of their uniqueness and familiarity, provided domain validation is performed. The book concludes that authentication method selection must balance security requirements, user behavior, and platform expectations, favoring stronger methods implemented from the start rather than relying on post-login detection.
Related articles
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.
The Real Costs of Using Claude and GPT for Russian Businesses Exposed
Accessing generative AI models like Claude and GPT has become straightforward for Russian companies, yet calculating their true expenses remains complex. Hidden factors such as intermediary commissions, currency conversion rates, taxes, and the often-overlooked costs of model reasoning tokens can double or triple initial estimates. Founder Vitaly Nagay of the Heli service analyzed these financial and organizational risks for Russian firms relying on foreign AI providers. In one example, a support department processing 20,000 monthly queries sees costs rise from $240 to $480 when reasoning tokens are included. Nagay recommends evaluating providers by dividing actual ruble charges by the model's official dollar pricing to reveal hidden markups. Additional concerns involve data control, document compliance, and access history when employees use personal subscriptions. Companies are advised to verify billing details, data storage policies, and issue dedicated API keys with spending limits before procurement.