# Putting it all together

This section shows how to enable all available Derby defenses.

This example uses SSL encryption, NATIVE authentication, and both coarse-grained and fine-grained authorization.

- Starting a secured Network Server
  Bring up the server and turn on SSL.
- Creating and using a secure database
  Now the Database Owner creates an encrypted database, turns on coarse-grained authorization, and creates some data that everyone can read but only he can write.
- Stopping the secured Network Server
  Now you can bring down the secured server.

Parent topic: Part Two: Configuring security for Derby
Related concepts
Basic security configuration tasks
Configuring database encryption
Using signed jar files
Configuring SSL/TLS
Understanding identity in Derby
Configuring user authentication
Configuring user authorization
Restricting file permissions