The 7 Most Wanted Iranian Hackers By the FBI

The Federal Bureau of Investigation (FBI) has lengthened its Most Wanted List by adding seven Iranian hackers who are accused of attacking a range of US banks and a New York dam.

On Thursday, the United States Department of Justice (DoJ) charged seven Iranian hackers with a slew of computer hacking offences for breaking into computer systems of dozens of US banks, causing Millions of

IOC: a buzz word and a hot topic, but do we really know its capabilities?

IOCs

 

In order to secure and maintain an IT infrastructure, it is vital to know what is going on in the network that the Endpoint is running on. This means that managers and other stakeholders need to know if something unusual is happening within the corporate network. When we use the word “unusual” we mean any potential threat or suspicious activity that may have happened or is currently happening within the company infrastructure.

Until now, the main service that most security-intelligence businesses could offer us was a subscription alerting us of the latest threats, malware, IPs and URLs with malicious intent; etc.  Adding this information to an infrastructure’s perimeter security system has allowed engineers to proactively plan and prepare, and has helped them to detect and prevent any threats their company may otherwise be susceptible to. In the IT industry, these updates are very common and companies will not hesitate to pay a certain amount in exchange for the latest updates offered.

With this service, it’s easy to prevent malware vulnerabilities but can we fully protect our infrastructure? The answer is yes, but the value of these services is high and the lifetime of their deliverables, in general, is very short.  So, what can we do to boost our protection?

 

The next generation in threat detection.

Every day, security analysts piece together different events related to new threats. When it comes to cyber-security, these analysts need a faster way to share information regarding the incident and must have the fastest response time possible. These incidents can be a simple observable (an IP, URL, a hash…), or can be more complex, requiring advanced analysis and reverse engineering. When all of these patterns have been assembled, the result is what we call an Indicator of Compromise (IOC). This may sound foreign to most of us, but security analysts should be familiar with the concept of an IOC and all of its capabilities.

So what exactly is an IOC?

In computer forensics, an IOC is an activity and/or malicious artifact identified on a network or an Endpoint.  We can identify these IOCs and can thus improve our abilities to detect a future attack.

 

Seems simple, right?

If we focus on their use cases, you can be described from a list of indicators to a full incident cybersecurity for analysis, research and/or response and can get answers to ‘What, Who, Why, How, Where and When ‘of the incident. Some of these use cases might be:

  • Inbox e-mails with falsified information (phishing)
  • Malware behavior patterns
  • Discovery of a specific vulnerability and actions to combat it
  • The distribution of a list of IPs related to Command and Control
  • Discovery of a specific vulnerability and actions to combat it
  • Sharing policies and patterns of behavior related to a certain incident (automatically or manually) so they can be exploited by third parties.

We can also use a list of standards to discover the IOC based on its needs (e.g., subsequent detection, characterization or sharing).

This was a brief introduction to IOCs.  We will continue to investigate this issue in the articles we publish in the future and our goal is to help security analysts understand more about the following:

  • What standards currently exist to help us find IOCs? State of the art, benefits, Use Cases…
  • How can we characterize an Indicator of Compromise?
  • How are we able to share Indicators of Compromise?
  • IOC Accuracy: Quality, life-time…

The post IOC: a buzz word and a hot topic, but do we really know its capabilities? appeared first on MediaCenter Panda Security.

Mac OS X Zero-Day Exploit Can Bypass Apple's Latest Protection Feature

A critical zero-day vulnerability has been discovered in all versions of Apple’s OS X operating system that allows hackers to exploit the company’s newest protection feature and steal sensitive data from affected devices.

With the release of OS X El Capitan, Apple introduced a security protection feature to the OS X kernel called System Integrity Protection (SIP). The feature is designed

CESA-2016:0512 Important CentOS 7java-1.7.0-openjdk Security Update

CentOS Errata and Security Advisory 2016:0512 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0512.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
0218ebf5593d9f4d474a891adeaa7e2b9c812d3982b1f8d843c43ac344d5f374  java-1.7.0-openjdk-1.7.0.99-2.6.5.0.el7_2.x86_64.rpm
78fa6b16e778ae1ec7de0a8314880d1788934cd9db47cfc8a2beb334a4bce5b4  java-1.7.0-openjdk-accessibility-1.7.0.99-2.6.5.0.el7_2.x86_64.rpm
607ba12a40f7a8038347a4b6e66b50e27dc3547480b4de7bf9bace6e3ffad2f2  java-1.7.0-openjdk-demo-1.7.0.99-2.6.5.0.el7_2.x86_64.rpm
3ca3726679cadbdcc6f56c597233935d7be4331caadec71fb4fac34632928993  java-1.7.0-openjdk-devel-1.7.0.99-2.6.5.0.el7_2.x86_64.rpm
f2ebdc0121ea05b1318e06fff13b81d76b50188f434c8a5fdf8c44a6a79e1f79  java-1.7.0-openjdk-headless-1.7.0.99-2.6.5.0.el7_2.x86_64.rpm
07146b95e0e01665f3b90a2df36b40647edc4ac58acfddde99972d00d5c2b22b  java-1.7.0-openjdk-javadoc-1.7.0.99-2.6.5.0.el7_2.noarch.rpm
753d34d69a0022c91990bfefdb04f11fac76dab60820ab21f64d6a78262e0e4c  java-1.7.0-openjdk-src-1.7.0.99-2.6.5.0.el7_2.x86_64.rpm

Source:
bcfec41d401e7ee8f55423c763774fa67a7bd0945ccbd26e8a43b09ae32146ba  java-1.7.0-openjdk-1.7.0.99-2.6.5.0.el7_2.src.rpm



CESA-2016:0513 Critical CentOS 7java-1.8.0-openjdk Security Update

CentOS Errata and Security Advisory 2016:0513 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0513.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
240e10e19995010fbed0072baca5ec4a633d291fe04b2637a9e08f5544ef3cba  java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64.rpm
1cdfb9ffdf581a72a386c6b452bd78445d3de8c7e32fe370345b7ff486c23b16  java-1.8.0-openjdk-accessibility-1.8.0.77-0.b03.el7_2.x86_64.rpm
43d8af1a3c1fac2ee7ef3bd21bd14fc1b4bc9b42ec08d15d49721cf691543e40  java-1.8.0-openjdk-accessibility-debug-1.8.0.77-0.b03.el7_2.x86_64.rpm
72d5dfad9b31d471e005b702de70788f49c217e32de6d0c871978d6fffdea7e1  java-1.8.0-openjdk-debug-1.8.0.77-0.b03.el7_2.x86_64.rpm
57d27276f4caf395da5e05454ca213efef649b4f3d887699dd6f5a9a77e99099  java-1.8.0-openjdk-demo-1.8.0.77-0.b03.el7_2.x86_64.rpm
c1bea843f1135cc46f5b64a830eee602aa25400b19ff25bca43f040f04381b73  java-1.8.0-openjdk-demo-debug-1.8.0.77-0.b03.el7_2.x86_64.rpm
708cacbf6901647e7ee38218820a609fd3e44993ce855488f9ad6ad2370646a4  java-1.8.0-openjdk-devel-1.8.0.77-0.b03.el7_2.x86_64.rpm
0c9ab4e61a75a04d81624facb6d8b3e7ffc15c0f126e0d2e939b13ecffc74048  java-1.8.0-openjdk-devel-debug-1.8.0.77-0.b03.el7_2.x86_64.rpm
adc8065a67d634d9660aec4d30324877f504fe74091158994bc21f574bcc6645  java-1.8.0-openjdk-headless-1.8.0.77-0.b03.el7_2.x86_64.rpm
45240102ce2f329657daaa2bc65421e4a3b02f2b38922ee3bf5821aef461b0d6  java-1.8.0-openjdk-headless-debug-1.8.0.77-0.b03.el7_2.x86_64.rpm
f108a5a03b17fcd5a81aada269a13a99d9ba3781194d11b47f1fa7e11668860c  java-1.8.0-openjdk-javadoc-1.8.0.77-0.b03.el7_2.noarch.rpm
3b33a164e77715f5bde17510de121850060b40db6d952dfa693b8a0c8fa25148  java-1.8.0-openjdk-javadoc-debug-1.8.0.77-0.b03.el7_2.noarch.rpm
331504d5730812be6c9bb864cbbac6814bb5d64015794beda041a41b07048880  java-1.8.0-openjdk-src-1.8.0.77-0.b03.el7_2.x86_64.rpm
c362139f9034f1980c125fcf41b4e21cbe9e371cabc0905b32d5bb01576b4b5a  java-1.8.0-openjdk-src-debug-1.8.0.77-0.b03.el7_2.x86_64.rpm

Source:
b68d59a247e68a51b9abb5d82453bdf7ffc561883dd55ec3cd4d9faf663aa2d9  java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.src.rpm



CEEA-2016:0517 CentOS 7 tzdata Enhancement Update

CentOS Errata and Enhancement Advisory 2016:0517 

Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0517.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
561e5bff553e41cd861952d054fcbdbdc474ec590bb56891546d938df4b14059  tzdata-2016c-1.el7.noarch.rpm
68825d33f45a6014a1df340cb4c5750b29bfa1383c0fcd6c2f70962bf63ac086  tzdata-java-2016c-1.el7.noarch.rpm

Source:
5dc1a988e18b42b35f5e2ff734d0184616f707665534809f71a87c94a35e5e17  tzdata-2016c-1.el7.src.rpm



CEEA-2016:0517 CentOS 5 tzdata Enhancement Update

CentOS Errata and Enhancement Advisory 2016:0517 

Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0517.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
907d8ba5f5fc5dc90b2a0f6e45fffe88baa8ddb64ba8c827933f6d3e7889a0af  tzdata-2016c-1.el5.i386.rpm
c2d5c77bd3d7c0f4e91154788dc421d8eb9dfd56f3e63a3e694bbafaaad6a556  tzdata-java-2016c-1.el5.i386.rpm

x86_64:
771e0c5c024f8420c3a820b83b2ce4f7a156b1e93e860533af12572bce8d4a04  tzdata-2016c-1.el5.x86_64.rpm
faeb5dfe3c89f273889af2a007331c8a8b02d7561bd2362e2a8753e2f3f901c1  tzdata-java-2016c-1.el5.x86_64.rpm

Source:
85d9fc61a8a60a8c4d19d3fae19f651c4f149ebea58cb742800492f699d0a62f  tzdata-2016c-1.el5.src.rpm



CEEA-2016:0517 CentOS 6 tzdata Enhancement Update

CentOS Errata and Enhancement Advisory 2016:0517 

Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0517.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
06d77cccd4ca9fdede69e03cb03ea066f4fe65f279a083356705e429adbda7c5  tzdata-2016c-1.el6.noarch.rpm
a4e1c676af9c38e3cb92474d4b514070c1bf124148c86968d9c68678da2d13ae  tzdata-java-2016c-1.el6.noarch.rpm

x86_64:
06d77cccd4ca9fdede69e03cb03ea066f4fe65f279a083356705e429adbda7c5  tzdata-2016c-1.el6.noarch.rpm
a4e1c676af9c38e3cb92474d4b514070c1bf124148c86968d9c68678da2d13ae  tzdata-java-2016c-1.el6.noarch.rpm

Source:
79ca2aac587840574b85e7d2350b445ac79a8c3cecab20bf832e6a0faddefb53  tzdata-2016c-1.el6.src.rpm



CESA-2016:0512 Important CentOS 5java-1.7.0-openjdk Security Update

CentOS Errata and Security Advisory 2016:0512 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0512.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
0601f0acd3975576f68ed47e13667f509139768c208317f0d57659a6f23a7ddf  java-1.7.0-openjdk-1.7.0.99-2.6.5.0.el5_11.i386.rpm
7f10524617009542be7ef5f12f1a49cfff24e94992602b545e5a9b4a224571b1  java-1.7.0-openjdk-demo-1.7.0.99-2.6.5.0.el5_11.i386.rpm
f38e3be18d354c31cd7f17d3de55f2678f5d9deec7dcc5a6751f2a88dea1e780  java-1.7.0-openjdk-devel-1.7.0.99-2.6.5.0.el5_11.i386.rpm
3e5b6c1fe5f20c9ead9c3f06bc15903db03d64997bc3a630c957b8c1159ee87a  java-1.7.0-openjdk-javadoc-1.7.0.99-2.6.5.0.el5_11.i386.rpm
145f50f554c1932db35a4cb5955ab020f942fd3d5970cb2a9c3023753dfbd3e9  java-1.7.0-openjdk-src-1.7.0.99-2.6.5.0.el5_11.i386.rpm

x86_64:
a93ea511993d4be788684118f86d1b456f5e03d21cef66ee6b69d1d46f8141a5  java-1.7.0-openjdk-1.7.0.99-2.6.5.0.el5_11.x86_64.rpm
51a057b2f0d78f407d37c29d8c98b8fe4983478a725491bc44988f2138b54297  java-1.7.0-openjdk-demo-1.7.0.99-2.6.5.0.el5_11.x86_64.rpm
6ed6437ec8bed548130d57bde5cdce2bbf4097d31938020be2828f4560f1a2ab  java-1.7.0-openjdk-devel-1.7.0.99-2.6.5.0.el5_11.x86_64.rpm
6c1c5c676aa7f2a9ae62959a70f3781d8c4526a9719258f2dc773bb5361ddb74  java-1.7.0-openjdk-javadoc-1.7.0.99-2.6.5.0.el5_11.x86_64.rpm
373696b5d89dfb3e278945ef42809351efe8ba7ce2640edbff2d9659d408872e  java-1.7.0-openjdk-src-1.7.0.99-2.6.5.0.el5_11.x86_64.rpm

Source:
cea109ea3ad0f7db884711c879d326b82324ffd2f468c93ffd7f8211bd84c77a  java-1.7.0-openjdk-1.7.0.99-2.6.5.0.el5_11.src.rpm



CESA-2016:0514 Important CentOS 6java-1.8.0-openjdk Security Update

CentOS Errata and Security Advisory 2016:0514 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0514.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
6b59479e59db490421e0b789d3285564138cd5ab70d1bb35e3a4b6238b8b8eab  java-1.8.0-openjdk-1.8.0.77-0.b03.el6_7.i686.rpm
972a29ec793bcbd69d18c74dabe951a28f73e376088bec2e9f0998801c1f5c17  java-1.8.0-openjdk-debug-1.8.0.77-0.b03.el6_7.i686.rpm
c0f4e0bca639d0ed8ae58ad59664e7dba5e95014d17cf6f38259d10234497a6e  java-1.8.0-openjdk-demo-1.8.0.77-0.b03.el6_7.i686.rpm
5e302648e9e135177d32c85a11c63e923e05a9c2886b4311bffa9a4c2c65c0d9  java-1.8.0-openjdk-demo-debug-1.8.0.77-0.b03.el6_7.i686.rpm
7f5183b652d8bc1a8ae1096f1606d17d793f9132f1f871d0c70a29a824764d8d  java-1.8.0-openjdk-devel-1.8.0.77-0.b03.el6_7.i686.rpm
a5b9386ad7e05e6357451e59b013c1a9150e9140b617267b2d21aadc56bf63b3  java-1.8.0-openjdk-devel-debug-1.8.0.77-0.b03.el6_7.i686.rpm
761413afb257eb72963311d6995f8d3b4a8db65b6a4e037910dbfdd41fede524  java-1.8.0-openjdk-headless-1.8.0.77-0.b03.el6_7.i686.rpm
254037d7872e2ea4013f8af44aed7f6e00a02f03483c6048c8ddda1bdeefc581  java-1.8.0-openjdk-headless-debug-1.8.0.77-0.b03.el6_7.i686.rpm
f22d24389aa542bc2f9cbb9dff8d1b9e98da0194883585e89cc2aebfa6fda4be  java-1.8.0-openjdk-javadoc-1.8.0.77-0.b03.el6_7.noarch.rpm
b36e0af0f2d10bc7b965361b5e9f1542271fe5d52ee6c65bad79b89f5cf3ba42  java-1.8.0-openjdk-javadoc-debug-1.8.0.77-0.b03.el6_7.noarch.rpm
e04350565daaafb98e5b63a3504cac50dc0ff8bd5be01e67565d116bb9402e55  java-1.8.0-openjdk-src-1.8.0.77-0.b03.el6_7.i686.rpm
f8a2dde3fe249b0e13601f6ba5074bd62c55fbabe6c0ef72551767dd21828369  java-1.8.0-openjdk-src-debug-1.8.0.77-0.b03.el6_7.i686.rpm

x86_64:
7b895f93cf9072c40526e3624570c2e0e3187b82cded5d90a2d34d119e47fff7  java-1.8.0-openjdk-1.8.0.77-0.b03.el6_7.x86_64.rpm
d1e63f0a00271c37785c3bf807e44bb028f52f05ff59e300a9f6489ff73b089a  java-1.8.0-openjdk-debug-1.8.0.77-0.b03.el6_7.x86_64.rpm
fa17b66bb598c04a63e518b0beec9b79bfafa9ba3787bb610ee500385a5468ac  java-1.8.0-openjdk-demo-1.8.0.77-0.b03.el6_7.x86_64.rpm
74fd22b68b7b9ce5c20627196547dd1dc67c3cc38676907d43970e59addc15b8  java-1.8.0-openjdk-demo-debug-1.8.0.77-0.b03.el6_7.x86_64.rpm
0a7824a3813e173a19c91c30b7d73ea1fcbac2e644570beb68a043946a8600f8  java-1.8.0-openjdk-devel-1.8.0.77-0.b03.el6_7.x86_64.rpm
e3399fa82c52cdf86b3d4c7c8fece1d3f786d57af2475034792f038c233d9300  java-1.8.0-openjdk-devel-debug-1.8.0.77-0.b03.el6_7.x86_64.rpm
7234e602deb6601ec6b0436eae4956339c08d5cad9ee6ba82515ab85fd43cd17  java-1.8.0-openjdk-headless-1.8.0.77-0.b03.el6_7.x86_64.rpm
44939403c57b92a00809455d16e23b8ef8b14a78ee9e1932be289b15e1a714cd  java-1.8.0-openjdk-headless-debug-1.8.0.77-0.b03.el6_7.x86_64.rpm
f22d24389aa542bc2f9cbb9dff8d1b9e98da0194883585e89cc2aebfa6fda4be  java-1.8.0-openjdk-javadoc-1.8.0.77-0.b03.el6_7.noarch.rpm
b36e0af0f2d10bc7b965361b5e9f1542271fe5d52ee6c65bad79b89f5cf3ba42  java-1.8.0-openjdk-javadoc-debug-1.8.0.77-0.b03.el6_7.noarch.rpm
286af04b050a75a9b65378646d15751099eebc33ff7edfc6d887027b06ade010  java-1.8.0-openjdk-src-1.8.0.77-0.b03.el6_7.x86_64.rpm
6bc3efdf0206cc93de67b8523e0338106b7e4e01e1b0d69526c8129c6a178e43  java-1.8.0-openjdk-src-debug-1.8.0.77-0.b03.el6_7.x86_64.rpm

Source:
a430de9d631dc13420600b78802a1671e04edd61651cbf8a52c42e49bee1cf9f  java-1.8.0-openjdk-1.8.0.77-0.b03.el6_7.src.rpm