## Why is this an issue?

The point of having custom exception types is to convey more information than is available in standard types. But custom exception types must be `public` for that to work.

If a method throws a non-public exception, the best you can do on the caller’s side is to `catch` the closest `public` base of the class. However, you lose all the information that the new exception type carries.

This rule will raise an issue if you directly inherit one of the following exception types in a non-public class:

- Exception
- SystemException
- ApplicationException

## How to fix it

### Code examples

#### Noncompliant code example

    internal class MyException : Exception   // Noncompliant
    {
      // ...
    }

#### Compliant solution

    public class MyException : Exception
    {
      // ...
    }

## Resources

### Documentation

- OWASP - Top 10 2017 Category A10 - Insufficient Logging & Monitoring
- Exception
- SystemException
- ApplicationException
- Access modifiers
- Exceptions and Exception Handling