Tuesday, December 5, 2017

Solar Panels as a Target

            Alternative and renewable energy sources have become more important and visible over the last few years. This is due to many factors, including the price in oil fluctuating, oil being a finite resource, the nation focusing on being less dependent on oil from other countries, and the clear view of the environmental concerns.
            As the alternative energy sources have been produced to a greater level, there are more choices for consumers. Early on, there was solar and wind. As time passed more products within each were added and to a greater extent. For instance, there were consumers and users using a few of these on their property. Now there are solar farms across the U.S. and wind farms on land and in the sea. As a bi-product with the increased number of products is the security testing. There are by far more products available, and security has been applied at a rudimentary level or brushed aside.
Target
            This testing methodology was put into place with a recent product. With solar panels, an essential piece of the equipment is the inverter. This allows the solar panel to convert the DC (direct current) to AC (alternating current). With the subject solar panels, this was connected to the internet. The vulnerability noted was researched and published by the Dutch InfoSec firm ITsec.
Exploit
            The security researcher found 17 vulnerabilities. With this attack, the security researcher was able to take control of the solar panel. If the attacker were able to gain control over a significant number of solar panels, much like the IoT bot army, the solar panels could be turned off or on at the same time. Individually, this seemingly would not appear to be a significant issue. The integral portion of this is that the solar panels are connected to the grid. If this were to be done with a large number, there would be a significant fluctuation in the power grid. This would cause a rather large and nearly instant power imbalance, which could force the grid to power off.


            From a third party’s view, this would not be an issue. The additional component not noted in significant numbers in the U.S. is the connectivity. With this factor, a large number of solar panels being turned off or on at any distance would be a rather significant detriment for the utility. 

Gorilla Glue Data Not Secure

            Gorilla Glue is known for their excellent set of products, and also the commercials. What has not been overly publicized, naturally, is the compromise from last year. The attack was spearheaded by The Dark Overlord. The hackers had previously attacked medical organizations and demanded a significant ransom. The group also attacked West Park Capital, an investment bank. In this instance the attacker claimed to have over 500GB of data from Gorilla Glue. Included in this mass amount of data was IP, product designs, access to company email accounts, Dropbox, financial spreadsheets, invoices, strategy documents, presentations, contracts with banks, and other confidential documents (Cox, 2016; Bisson, 2016). This was a rather brazen claim. Without some form of authentication, there would be a minimal amount of credibility. To circumvent this issue, The Dark Overlord forwarded 200MB of files to Motherboard (Cox, 2016). These were also forwarded to Gorilla Glue as evidence.
Ransom
            As with any attack of this nature, it is presupposed that there would be the threat of releasing the data if a fee is not paid. This was not an exception. As with the two prior victims (a medical group and the investment bank), Gorilla Glue was provided with a “handsome business proposal” (Bisson, 2016). There were two primary options-pay or don’t. The paying has issues of not receiving the data, the data being released later, malware being left on their system, etc. With not paying the immediate threat would have been the release of their data, short-term loss of respect, and damage.

References
Bisson, D. (2016, November 18). Gorilla glue finds itself in sticky situation after hackers steal data. Retrieved from https://www.grahamcluley.com/gorilla-glue-finds-sticky-situation-hackers-steal-data/

Cox, J. (2016, November 17). Hackers claim theft of data from gorilla glue. Retrieved from http://motherboard.vice.com/en_au/read/hackers-claim-theft-of-data-from-gorilla-glue

Machine Learning to Assist with InfoSec

            Computers are rather adept at a large number of tasks, from the mundane to complex and dangerous. The users may want statistics applied to columns of numbers, list of prime numbers, or any other task that would require a computing ability within a parameter of steps. The systems, by design, process items faster, are able to complete complex computations at such a quicker pace, and are able to compare correlations faster than a human could ever fantasize about.
Given this speed, it is no wonder users are gladly able to hand-off the tasks requiring this level of processing so quickly. This makes life a bit easier for the user and more efficient for all parties, human and not.
Machine learning (ML) offers a number of benefits to industries not focused on nearly instant processing. This is especially true in the case with the InfoSec field. This industry has such a diverse population and set of duties, intuitively finding a match with the duties may take a bit of time. The Admin or other person responsible for this integration, at this point, is not able to just load this onto the servers and not maintain the program. This may be a completely workable option in the very near future, given Google’s new AI iteration, which learns on its own. This would need to be reviewed periodically for adjustments. This could be for the configuration itself, to adjust the algorithms, or other functionality.
ML and AI (eventually) is able to specifically assist with several InfoSec functions and issues. One area is to limit the spear phishing attack effectiveness. Phishing continues to be a significant issue. This has and continues to be exceptionally profitable for the attackers. This continues to be a severe detriment for the user, financially and operationally. These attacks steal and exfiltrate money, credentials, data and other items that may be of value which could be sold by the successful attackers. The attackers use social media, business websites, and other sources for the data to make the attacks a success. In general, the greater amount of data, the greater the potential for the attacker to mislead the target into clicking a link or a picture, visiting a malicious URL, or following other nefarious instructions to infect their systems. The ML algorithm may be used to assist with this. The ML algorithm may use the metadata located in the emails. This may be accomplished while maintaining the user’s privacy. The email header and a sampling of the email’s body makes this able to provide data as to if the subject email is representative of a malicious, spear phishing email. The ML algorithm is able to review the behavior evidenced by the email to gauge if this likely would be an phishing or spear phishing email.
            The ML algorithms are able also to work on watering hole attacks. These appear to be a perfectly legitimate website. With these though, the sites or applications would have been compromised, or the sites themselves may be false and malicious. These may also lure people to put in their credentials for other sites. In this case, the ML algorithm may identify interactions encountered before, creating a baseline of behavior to use. This may be compared to the present activity to gauge if this would likely be a malicious activity.
            This list is clearly very short and is only a small sample of the capabilities and potential uses for ML in InfoSec. There are many more places and uses for ML and the respective algorithms. This will be a significant benefit for the users, business, and a detriment for those intent on attacking the enterprise. 

'Tis the Season

Seemingly every year about this time, the phishing campaigns are presented to the consumers. The phishing emails have taken various forms to the consumers. There have been the emails from “shipping carriers” to several individuals stating their packages, all with the same tracking number, is out for delivery. “Vendors” forwarding emails with their new products you need to purchase for your friends and family as the perfect gifts are regularly encountered. These may be also time oriented, stating the Cyber-Monday sale is being extended for a very limited amount of time, so you need to click on the link for the retailer to have the special discount code. These emails are an attractive nuisance, yet are still effective to a point.
This year, I did receive an interesting contact. This was in the form of smishing via text message. The form was “Notice-[phone number] from [Bank]. Code: Visa-Debit Locked. Call us now at 202-852-xxxx. Thank you.” This was notable as it utilized a few of the motivators a phishing attack normally would. During the holiday season, people need access to their funds for the normal everyday purchases, but more to the point for holiday shopping for family and friends. This message indicates, if the consumer believes it, they are cut off from their funds, which they would need. Also, there is the thought that someone may have compromised their account, otherwise what would make the bank cease activity on the account, until the consumer contacts them.
This is also a teachable moment. Bank’s do have this option available for their customers. The customers also have the option to receive other text messages with the account balance, checks clearing, or other activity on the account. The form of the text was relatively close to what would normally be encountered by the consumers. In this case, the phone number was highlighted. If the consumer were to utilize the ease of use and press the option for the phone to call, there could have been a significant issue. The consumer should, as with emails, not presume the link is valid. In this instance the number was called, and the phone number allegedly to my bank was not in service and had been disconnected. The consumers may learn from this instance to make their experience more secure by not automatically trusting text messages as they arrive on their phone. 

Sunday, October 8, 2017

The need for bug bounty programs began years ago as a void formed. The manufacturers were producing their goods and services, as to be expected. An issue experienced was the manufacturers had the “first to market” mentality in place. There was and continues to be in certain markets, a hurry to design, engineer, and manufacture the product. The product needs to be the first in the marketplace for the consumer to purchase the unit. In theory, the manufacturer would be the market leader, and sell the maximum number of units and gain the market share. If the manufacturer were to wait, they would not be maximizing the sales volume and would be trying to catch up with their peers. This sales process methodology is unfortunately still prevalent. As of late this has been noted with routers, IP cameras, and other like equipment.

With these and other products security architecture was applied in various levels. This ranged from very little, with too many of the IoT products, to a moderate level of security applied. A contributing factor to this has been the lack of information security talent. This is a functiohe need for bug bounty programs began years ago as a void formed. The manufacturers were producing their goods and services, as to be expected. An issue experienced was the manufacturers had the “first to market” mentality in place. There was and continues to be in certain markets, a hurry to design, engineer, and manufacture the product. The product needs to be the first in the marketplace for the consumer to purchase the unit. In theory, the manufacturer would be the market leader, and sell the maximum number of units and gain the market share. If the manufacturer were to wait, they would not be maximizing the sales volume and would be trying to catch up with their peers. This sales process methodology is unfortunately still prevalent. As of late this has been noted with routers, IP cameras, and other like equipment.

With these and other products security architecture was applied in various levels. This ranged from very little, with too many of the IoT products, to a moderate level of security applied. A contributing factor to this has been the lack of information security talent. This is a function of the limited number of programs focused on this, newer programs not coming online at a quick enough pace, and a time lag once these are in place of at least three years prior to graduates entering the workforce.

One area growing in importance is vehicle security. The number of vehicles with embedded systems continues to grow. The autonomous vehicles are actively being tested on the roads used by other people presently. These vehicles are expected to be in full production within five years. These systems are being developed with the focus of having them operational in a timely manner with security being am secondary focus.

With the growing need for information security (InfoSec) professionals, there is an issue. In this specialty, there is a limited number of people that have the knowledge and expertise to attack the embedded systems in a vehicle. Most firms in this specialty do not allow their personnel to contribute to these bug bounty programs (Gray, 2017). This appears to be starting to relax, but is still a parameter to overcome.

With a bug bounty program, the sponsoring firm is able to add to their baseline of security. With vehicles, there are ample areas to research. The connected and autonomous vehicles in use today tend to be more computers on wheels than anything. From an administrative side, a bug bounty program is easier with a vehicle that has been sold for years. This allows for more vehicles and modules to be tested, as there are more vehicles on the lots and junkyards. With the new vehicles an issue could be, dependent on the circumstances, the cost. The new vehicles cost upwards of $30k new. The internal client may not want to part with two or three vehicles due to this constraint on their budget. With the junkyard vehicles, these not have all the original equipment due to an accident or other force, however many of the modules would be intact and perfectly testable.  bounds. More of the manufacturers are producing more connected vehicles, applications, and hardware.

The bug bounty programs are a welcome addition to the InfoSec environment for those manufacturers that without an internal testing program. This has and will continue to provide knowledge re: the vulnerabilities that may not normally be found.n of the limited number of programs focused on this, newer programs not coming online at a quick enough pace, and a time lag once these are in place of at least three years prior to graduates entering the workforce.

One area growing in importance is vehicle security. The number of vehicles with embedded systems continues to grow. The autonomous vehicles are actively being tested on the roads used by other people presently. These vehicles are expected to be in full production within five years. These systems are being developed with the focus of having them operational in a timely manner with security being am secondary focus.

With the growing need for information security (InfoSec) professionals, there is an issue. In this specialty, there is a limited number of people that have the knowledge and expertise to attack the embedded systems in a vehicle. Most firms in this specialty do not allow their personnel to contribute to these bug bounty programs (Gray, 2017). This appears to be starting to relax, but is still a parameter to overcome.

With a bug bounty program, the sponsoring firm is able to add to their baseline of security. With vehicles, there are ample areas to research. The connected and autonomous vehicles in use today tend to be more computers on wheels than anything. From an administrative side, a bug bounty program is easier with a vehicle that has been sold for years. This allows for more vehicles and modules to be tested, as there are more vehicles on the lots and junkyards. With the new vehicles an issue could be, dependent on the circumstances, the cost. The new vehicles cost upwards of $30k new. The internal client may not want to part with two or three vehicles due to this constraint on their budget. With the junkyard vehicles, these not have all the original equipment due to an accident or other force, however many of the modules would be intact and perfectly testable.  bounds. More of the manufacturers are producing more connected vehicles, applications, and hardware.

The bug bounty programs are a welcome addition to the InfoSec environment for those manufacturers that without an internal testing program. This has and will continue to provide knowledge re: the vulnerabilities that may not normally be found.

Monday, September 19, 2016

Petya Resolved!

Ransomware has become well-known over the last few years. The effects have been devastating to the consumer and commercial victims. Hospitals have had to pay in order to gain access to their files. At times, there have been no alternatives.
Ransomware had been used to encrypt data, files, or hard drives with a robust enough algorithm so it would take a year or years to guess the decryption key. Without this, the data is simply jumbled letters. A payment is generally demanded for the decryption key. This amount would vary in amount and would need to be paid within a certain number of days. If not paid within the attacker imposed timeframe, the deviant may not accept the funds and provide the key, or increase the fee for the decryption key.
Unfortunately for consumer and commercial enterprises, this has become more prevalent (Ginos, 2016). The deviants have noted the effort needed for the attack (spam email) in comparison to the potential fees to be collected. This has become lucrative for them based on this simple equation. This activity has been particularly rampant in the healthcare industries, as they need access to the patient medical records.
Some have no choice but to pay. If there are no recent back-ups, or the back-ups are corrupt or were not done there truly is not a choice if the data that is encrypted by the third party is of any consequence or the entity has to have it to operate, as in the case of hospitals.
This is not a new avenue for the criminals. Although much more common recently this has been an active pursuit for years. Prior versions of this included Cryptowall, TeslaCrypt, and Locky (Zorabedian, 2016).
Petya
With this specific sample of ransomware, the users statistically are lucky. Although this was, prior to the decryption methods, a true issue to the infected users and more importantly to their systems, Petya has not been seen abundantly (Zorabedian, 2016).
In general, the prior mode of operations had been to encrypt files. This is where the data was located the people needed for home or work. As this is the case, there would be a greater possibility of them paying. This is a clear detriment for the infected clients.
If this was not bad enough, Petya provided a new twist. This was coded specifically to also encrypt the master file table (MFT) (Bisson, 2016b; Ducklin, 2016). Petya also replaces the master boot record (MBR) with a malicious loader (Zorz, 2016a; Mimoso, 2016; Zorz, 2016b; Torres, 2016; Constantin, 2016).
As with other ransomware samples, this also had a target market in mind. The attackers sent the ransomware to mostly companies in Germany (Mimoso, 2016). The specific intended victims were the HR departments (Zorz, 2016a).
Petya also followed suit as there was a time limit involved for the payments. The user with the infected system had a week to pay the fee. After this the fee would double (Torres, 2016).
Method of Delivery
In order to get the most victims infected, a social engineering tactic was used. The user in the HR department receives the email. This appears to be from a job-seeker, but is really the deviant, with a malicious payload in the spam email. The file enclosed in the spam email appears to be a CV or a resume, which is what the HR department would expect (Zorz, 2016a; Ginos, 2016). There may also be a link to a dropbox file (Mimoso, 2016). Instead of an innocent file being downloaded, Petya is installed. The file is not a .doc or .docz file that is attached is an executable (Zorz, 2016a; Bisson, 2016). The HR department may not be that tech savvy and may not even notice it. The MBR is replaced with a malicious loader (Mimoso, 2016). After all the steps were done, the user would not receive the blue screen of death. After the infection has occurred, the ransomware demands approximately $400 in bitcoin for the decryption key (Torres, 2016; Thomson, 2016; Constantin, 2016; Bisson, 2016b; Mimoso, 2016b).
Encryption Cracked
Any encryption is valid only when it is not cracked. Once this is done, the encryption itself is only a speedbump. In this case the encryption was done with the Salsa 10 algorithm (Thomson, 2016). This has a less powerful encryption than the Salsa 20. Fortunately, there are tools that have been created to decrypt Petya (Zorz, 2016b). With this tool in hand, the computer is once again usable for more than just a boat anchor.
In late March 2016, an analyst specializing in malware (Hasherezade) wrote a decoder which was coded to extract the key needed to decrypt the ransomware (Zorz, 2016b; Zorz 2016c). Another tool created by “Leo Stone” also accomplishes this (Zorabedian, 2016; Zorz, 2016b; Zorz, 2016c). The difference with this other option is this tool can be used also the computer is rebooted. This is also provided free of charge (Mendoza, 2016). The decryption process may take up to seven seconds (Reeve, 2016).
It should be noted this is a relative anomaly. Generally these are written not to be able to be cracked within a reasonable amount of time.


References


Abrams, L. (2016, March 25). Petya ransomware skips the files and encrypts your hard drive instead. Retrieved from http://www.bleepingcomputer.com/news/security/petya-ransomware-skips-the-files-and-encrypts-your-hard-drive-instead/
Bisson, D. (2016, March 29). Petya ransomware goes for broke and encrypts hard drive master file tables. Retrieved from https://www.grahamcluley.com/2016/03/petya-ransomware  
Bisson, D. (2016b, April 11). Infected by petya ransomware? Use this tool to unlock your files...for now. Retrieved from https://www.grahamcluley.com/2016/04/petya-ransomware-unlock-tool/
Constantine, L. (2016, March 28). Petya ransomware overwrites MBRs, locking users out of their computers. Retrieved from http://www.infowarold.com/article/3048713/security/petya-ransomware-overwrites-mbrs-locking-users-out-of-their-computers.html
Constantin, L. (2016b, April 11). Experts crack petya ransomware, enable hard drive decryption for free. Retrieved from http://www.pcworld.com/article/3054220/security/experts-crack-petya-ransomware-enable-hard-drive-decryption-for-free.html
Ducklin, P. (2016, April 4). New ransomware with an old trick: “Petya” parties like it’s 1989. Retrieved from https://nakedsecurity.sophos.com/2016/04/04/new-ransomware-with-an-old-trick-petya-parties-like-its-1989/
Ginos, I. (2016, March 26). Petya ransomware reportedly encrypts hard drives, manipulates operating system boot process. Retrieved from http://www.neowin.net/news/petya-ransomware-reportedly-encrypts-hard-drives-manipulates-operating-system-boot-process
Mimoso, M. (2016, March 29). Researchers learning more about petya ransomware. Retrieved from https://threatpost.com/researchers-learning-more-about-petya-ransomware/117068/
Mimoso, M. (2016, March 28). Petya ransomware encrypts master file table. Retrieved from https://threatpost.com/petya-ransomware-encrypts-master-file-table/117024/  
Reeve, T. (2016). Cure for petya engineered by anonymous security researcher. Retrieved from http://www.scmagazineuk.com/cure-for-petya-engneered-by-anonymous-security-researcher/article/488802/?DCMP=EMC-SCUK_Newswire&spMailingID=14201710&spUserID-NTAzOTUzMjgwNzES1&spJob...
Thomson, I. (2016, April 12). Infected with petya ransomware? Retrieved from http://www.theregister.co.uk/2016/04/12/petya_ransomware_free_fixit_tool/
Torres, J.C. (2016, March 28). Petya ransomware targets entice drives, not just files. Retrieved from http://www.slashgear.com/petya-ransomware-targets-entice-drives-not-just-files-28433671/  
Zorabedian, J. (2016, April 12). Petya ransomware decryption tools sets your files free. Retrieved from https://nakedsecurity.sophos.com/2016/04/12/petya-ransomware-decryption-tool-sets-your-files-free/
Zorz, Z. (2016a, March 29). Petya ransomware encrypts files, disks, locks users out. Retrieved from https://www.helpnetsecurity.com/2016/03/29/petya-ransomware-locks-computers/
Zorz, Z. (2016b, April 11). Petya ransomware encryption has been cracked. Retrieved from https://www.helpnetsecurity.com/2016/04/11/petya-ransomware-encryption-cracked/
Zorz, Z. (2016c, April 11). Petya ransomware encryption has been cracked. Retrieved from https://www.helpnetsecurity.com/2016/04/11/petya-ransomware-encryption-cracked/



Thursday, September 15, 2016

Stop Looking at Me: The FDIC’s View of Cybersecurity

                Information security is pertinent to all businesses. This also reaches across all industries. At times, this is fully applied and at other times lacking. An example of the latter has been the breach with the Office of Personnel Management in 2014 with over 21M personnel records being stolen (Gordon, 2016). Although devastating for the consumer victims, this is likewise a concern for the targeted business. As of mid-2016, there was one industry however that was being targeted more often than not. This recent example was directed at the banking industry globally. This involved the Swift network.
                Another global example familiar to the US involves weak cybersecurity in the banking system and the Federal Deposit Insurance Corporation (FDIC).
Attack Period
                The target for the attacks was rather unique. For the most part, an attacker is seeking data that could be sold on the dark web or other areas. This may be focused on a business with credit card numbers, personnel records, or health records. The FDIC in this instance was the target of the cyber-attack. At times these attacks are a single occurrence as the attacker breaches the system during one, prolonged attack. In other circumstances, there may be a limited number of contacts for the attacker to pull the most amount of data for sale later. For this occurrence, the attacks however occurred in 2010, 2011, and 2014 (Lange & Volz, 2016; Sputnick, 2016, Gordon, 2016). This was a rather extended attack and allowed the attackers ample time to peruse through the files and servers at the FDIC.
Perpetrators
                Clearly this was a well-researched and planned attack due to the target-a federal entity. The higher risk and more valuable data involved, the more research may go into the enumeration of the target. This attack was investigated internally by the FDIC IT department. There was data left behind by the attackers. The data and research indicated the source of the attack was Beijing (Lange & Volz, 2016; Sputnik, 2016; Gordon, 2016). This attack has been in the form of an advanced persistent threat (APT) (Gordon, 2016).
How the Continued Attacks Were Successful
                The attacks covered a three year period, which is not the normal attack. In most other organizations, the attack on some level would have at least been noticed. In this case, there was a distinct lack of cyber-security efforts (Lange & Volz, 2016) and reporting.
                This continued to be an issue due to one glaring issue. The employees at the FDIC elected to actively hide the breach activities (Lange & Volz, 2016). This was an overt, deceiptful act (Pagliery, 2016) intended to mislead the remainder of the department and American society. Hiding this glaring and important issue was inept (Pagliery, 2016). This act was not done by one person but many people in the department.
                What makes this borderline unconscionable, heinous act is the FDIC’s top lawyers told the employees not to discuss the hacks via email. This directive was handed down by licensed attorneys who took the oath so there would not be a document trail. This is further exasperated as the CIO at the time actively misled the FDIC auditors as to the extent of the breach (Elfinger, 2016; Blake, 2016). This was at best ill-advised. This action only served to further expose confidential information and allow the attackers free reign over their system. This has effectually eroded any trust that was left in the US government.
                Had a business in the US had a breach and series of breaches allowing sensitive, confidential information to actively be exfiltrated from the business, and the breaches actively covered up, there would be a decidedly different result. The FTC would probably be diving very deeply into the business, applying an intense amount of pressure, and threatening legal action.
                This inaction, especially when the attacks were clearly known, was not prudent. The main rationale for this was brought to light much later. This was covered up expressly to protect the Chairman of the FDIC’s job (Lange & Volz, 2016). At the time the Chairman was Martin Gruenberg.
                The attack itself, over the years, was rather widespread. An attacker in general may look for one or two areas in an organization to attack. These may hold high profile information or confidential information, such as being finance or payroll oriented. In this instance though, it was not the case. The targets were 12 FDIC workstations and 10 servers over the years (Pagliery, 2016). The workstations were also varied in that these were not the usual targets, but included mainstream and the other executives systems (Sputnick, 2016). Overall during the years, there were an estimated 100 computers breached over the years since the first attack (Borack, 2016). Unfortunately, this was not the extent of the issue. There was also backdoors installed on the workstations and servers (Elfling, 2016; Gallagher, 2016).
Benefits to the Attacker
                This was not an attack simply for its own sake or for the person to be curious as to what was behind the wall. There was a distinct purpose in mind for the time and effort. There was a distinct purpose in mind for the time and effort. The point of this attack was the perpetrators apparently looking for “economic intelligence” (Lange & Volz, 2016). This much like earlier when the Chinese were “allegedly” were hacking the defense contractors for the plans and schematics.
Remediation
                After the report was published, naturally a significant amount of attention was paid to this. This was especially the case with the persons covering up the breaches. In response to this, the agency scheduled the policies to be updated. As part of this endeavor, the IT group is disengaging the users from using the USB drives, CDs, etc. from being used on their systems (Borak, 2016). The FDIC is also planning on upgrading their software. In addition, the FDIC IT group is working on a policy for employees who are leaving the FDIC employment. The plan is to have this done by October 28, 2016.
                This may correct inadequacies and vulnerabilities, however it completely misses the systemic issues with management, a lack of the ability to do the right thing, and licensed attorneys directing the issue to be covered up.
Troubling
                This intentionally deceitful set of acts is troubling and problematic on many levels. The FDIC intentionally hid the attacks and breaches over several years. This was directed on many levels. Clearly this was fraught with problems as the public was misled indirectly. Although there was not a direct lie told to the public, by hiding this, the agency was misleading the government, people, and institutions.
                The attacks went on for years. The extent of the attacks and the data viewed or exfiltrated may never be known. The FDIC does provide external facing data and statistics for the public to view. There is however more data that is confidential. The attackers may have accessed this at their leisure.
                This was hidden by all layers of the FDIC, from the C-suite and corporate attorneys downward. When the leadership is hiding this level of error from the public and all other agencies to protect one person, there is something inherently and systemically wrong. When the CIO and FDIC attorneys direct the staff directly and overtly to hide the breach of the system and confidential information, the problem is not isolated, but is with the organization.
                What is the most troubling is that this has not been overly noted in the news. A foreign country may have confidential data regarding the US banking industry. This is serious yet there has not been a mass amount of media involved with this. In a short period this may be forgotten by the public. What has not been brought forward is what could the other nation do with this information and data? What would happen with the banking industry if the nation used this data from the breach in a detrimental, persistent manner? This should make people concerned, yet this has been reduced in focus.














References
Asadorian, P. (Publisher). (2016, July 14). Security Weekly [Podcast]. Retrieved from https://securityweekly.com
Blake, A. (2016, July 13). FDIC let down its cyber defenses despite being hacked by Chines: House panel. Retrieved from http://www.washingtontimes.com/news/2016/jul/13/fdic-let-down-its-cyber-defenses-despite-being-hac/
Borak, D. (2016, July 14). Top FDIC officials weren’t fully informed on computer hacks chairman says. Retrieved from http://www.wsj.com/articles/top-fdic-officials-werent-fully-informed-on-computer-hacks-chairman-says-1468514182 
Daily Star. (2016, July 14). US banking regulator updates cyber security after data breach: Chairman. Retrieved from https://www.dailystar.com.1b/News/World/2016/Jul-14/362070-us-banking-regulator-updates-cyber-security-after-data-breach-chairman.ashx
Elfling. (2016, July 13). FDIC hacked by China, and CIO covered it up. Retrieved from http://www.dailykosbeta.com/story/2016/07/13/1394681/--FDIC-was-hacked-by-China-and-CIO-covered-it-up
Gallagher, S. (2016, July 13). FDIC was hacked by China, and CIO covered it up. Retrieved from http://arstechnica.com/security/2016/07/fdic-was-hacked-by-china-and-cio-covered-it-up/
Gordon, M. (2016, July 13). Chinese government suspected of hacking into FDIC computers. Retrieved from http://phys.org/news/2016-07-chinese-hacking-fdic.html
Lange, J., & Volz, D. (2016). Likely hack of U.S. banking regulator by China covered up: Probe. Retrieved from http://www.reuters.com/article/us-cyber-fdic-china-idUSKCN0ZT20M
Mimoso, M. (2016, July 13). Congressional report: China hacked FDIC and agency covered it up. Retrieved from https://threatpost.com/congressional-report-china-hacked-fdic-and-agency-covered-it-up/119276/
Pagliery, J. (2016, July 13). China hacked the FDIC-and US officials covered it up, report says. Retrieved from http://money.cnn.com/2016/07/13/technology/china-fdic-hack/index.html
Reuters. (2016, July 14). Why the FDIC is updating its cyber security policy after this data breach. Retrieved from http://fortune.com/2016/07/14/fdic-data-breach-cyber-security/ 

Sputnik International. (2016, July 13). China likely behind multiple computer breaches at US bank insurer. Retrieved from http://sputniknews.com/us/20160713/1042917703/us-cyber-security.html