Statically store computational security parameter

We are currently passing around many security parameters. Of these, one specific is a symmetric crypto security parameter. However, this parameter should be directly defined by the concrete encryption/hash functions used. I think it would be better to remove this as a parameter and let it be located as a final variable with the hash/encryption objects used instead.