UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Open a file:/// URL, such as file:///C:/
2. Click on the verbose chip..."Your connection to this site is not secure".
3. Press Ctrl+Shift+I to open Developer Tools, and then click on the Security tab..."This page is not secure."

What is the expected behavior?
file:/// URLs are considered secure since they are local.

What went wrong?
Even though they are not transmitted over the internet, file:/// URLs are considered insecure by both the verbose chip and the Developer Tools Security tab.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: