With the Cibet framework, it is very easy to add various control mechanisms into a JPA and/or EJB-based Java application. The actual version includes control schemes like Archiving (manipulation of domain objects; data and execution of business processes are archived). From the archived state, domain objects can be reconstructed and business processes can be re-invoked with the same parameters at any time. The archive entries are secured against manipulation to make them audit-proof and revision safe. Four-eyes principle: this scheme is an example of a dual control mechanism: A user wants to perform some critical data manipulation or business process. With an applied dual control mechanism, the action is not executed in the production system directly, but stored and postponed. A second user must check the data and the action and can approve or decline. Only when the second user approves, the data manipulation or business process is executed in the production system; otherwise it is discarded. An even stricter example for a dual control mechanism is the six-eyes principle. In this case, a third user must approve a data manipulation or business process before it will become productive.
Dummy Data Generator is a tool that generates dummy data for populating systems for testing. The data includes names, addresses, email addresses, phone numbers, and social "connections". Names are generated by using US Census data on the most common names. Email addresses are just a random string for the user portion and always use "example.com" for the domain. Currently the only output format is CSV.
Google Authenticator Demo is an implementation of two-factor authentication using the Google Authenticator that can be used on your own site or application. It allows you to register a user name and then log in using the information provided by the Google Authenticator. It also works with OATH HOTP compliant hardware tokens.
MASH is a modular, automated script harness. It allows users to implement simple harnesses that perform work external to a system. The framework will invoke that harness as outlined by an XML script. For example, when using the framework to test a system you could create a script that cleans and loads a database, FTPs some data, submits a login form, and verifies HTTP information. Harnesses can easily be built to do almost anything (many harnesses are provided), not just Web page verification. While harnesses are written in Java, the scripts may be run against any type of system as harnesses are intended to act as clients.