Libraries tagged by framework security

yet another Laravel 4 XSS (CI Based) & html input filter for laravel4

Go to Download

Server library for server side implementation of OAuth 1. Integrates easily with a framework, but can also be used outside of one.

Go to Download

shieldfy firewall component for codeigniter framework

Go to Download

Extension for Nette Framework: set presenters names to secure and they will be secured via http authentification. IAuthenticator service is used for validating user credentials.

Go to Download

Class to add scrypt hashing to the Phalcon framework. Requires scrypt extension.

Go to Download

SeznamCaptcha to Nette Framework

Go to Download

Zend Framework 3 module that provides complete integration of HTMLPurifier library

Go to Download

Zend Framework 2 module that provides complete integration of HTMLPurifier library

Go to Download

A security cryptography library for PHP. It can be used by different frameworks or pure PHP

Go to Download

Security signature component for Hyperf framework

Go to Download

Spatial is a MulitApi Clean Architectre Framework. Its Doctrine ORM for maximum performances and security.

Go to Download

A small, simple, and naked PHP MVC framework skeleton that encapsulates a lot of features also implements security layers.

Go to Download

Ramphor Framework is an Extended WordPress core to build a web app faster, security and friendly with WordPress and PHP Developers

Go to Download

# Summary The **NextGenPSD2** *Framework Version 1.3.6* (with errata) offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Go to Download

Remote Database Backup: Your Data, Securely Backed Up Anytime, Anywhere.

Go to Download