Recherche avancée

Sur d’autres sites (6519)

• ffmpeg transcoding stop after few seconds

  9 avril 2018, par Salem F

  Hi i’m trying to do this over week now with no success ,
  What’s i’m trying to do is transcoding video from live streaming source and downscale it with FFmpeg , but every time I start transcoding it broadcasting fro 11 Sec and stop . here last command I tried

    ffmpeg  -re  -i 'http://source.com/1034.ts' -preset ultrafast http://localhost:2052/feed1.ffm

  I tried to download the .ts file with IDM and it finish downloading the file on the exact 12 Sec that FFmpeg stop trans coding on it .

  does that means that FFmpeg download that file as one segment and not continued reading the source video As what video players does usually . BTW I tried with source with VLC player and it didn’t stop playing the the same source video .

  Edit :- I decide to pass FFmpeg command via FFserver config file ffserver.conf

  Launch ffmpeg -i 'http://source.com/1.ts' -copyinkf -codec copy   

  The stream works fine for a while but after testing couple sources I notice it’s struggle to trans-coding HD videos .

  I guess the issue with my VPS KVM server being very limited CPU and RAM ( 128MB only ) ! Since I tried using ultrafast preset but din’t solve the issue , another thing , I notice when I enable AVOptionVideo crf setting on ffserver.conf trans-coding runs bit smoothly without frame-rate dropping .
  Las my server uses Xeon L5520 CPU which is outdated CPU specially I gout 1/4 power of V single core (if they count HT it will be 1/8 of the real core ) :(

  Edit 2 :-

  # vlc -I dummy 'https://source.com/1034.ts' --sout '#standard{access=http,mux=flv,dst=localhost:2052}'
  
  VLC media player 2.2.8 Weatherwax (revision 2.2.7-14-g3cc1d8cba9)
  
  [09d3fdf0] pulse audio output error: PulseAudio server connection failure: Connection refused
  
  [09d279c0] core interface error: no suitable interface module
  
  [09c9b8f8] core libvlc error: interface "globalhotkeys,none" initialization failed
  
  [09d279c0] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
  
  [09d279c0] core interface error: no suitable interface module
  
  [09c9b8f8] core libvlc error: interface "dbus,none" initialization failed
  
  [09d279c0] dummy interface: using the dummy interface module...
  
  [b5e04ae0] access_output_http access out: Consider passing --http-host=IP on the command line instead.
  
  [b5e38ab8] ts demux: MPEG-4 descriptor not found for pid 0x101 type 0xf
  
  [b5e90ae0] packetizer_mpeg4audio decoder: AAC channels: 2 samplerate: 48000
  
  [flv @ 0xb5e33b40] dimensions not set
  
  [b5e06360] avformat mux error: could not write header: Invalid argument
  
  [b5e88ef0] core decoder error: cannot continue streaming due to errors
  
  [b5e90ae0] core decoder error: cannot continue streaming due to errors

  Here output with -loglevel verbose

  :~# ffmpeg -i http://source.com/1.ts -copyinkf -codec copy  -loglevel verbose  http://127.0.0.1:8090/feed1.ffm
  
  ffmpeg version 2.6.9 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 4.9.2 (Debian 4.9.2-10)
  
    configuration: --prefix=/usr --extra-cflags='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security ' --extra-ldflags='-Wl,-z,relro' --cc='ccache cc' --enable-shared --enable-libmp3lame --enable-gpl --enable-nonfree --enable-libvorbis --enable-pthreads --enable-libfaac --enable-libxvid --enable-postproc --enable-x11grab --enable-libgsm --enable-libtheora --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libx264 --enable-libspeex --enable-nonfree --disable-stripping --enable-libvpx --enable-libschroedinger --disable-encoder=libschroedinger --enable-version3 --enable-libopenjpeg --enable-librtmp --enable-avfilter --enable-libfreetype --enable-libvo-aacenc --disable-decoder=amrnb --enable-libvo-amrwbenc --enable-libaacplus --libdir=/usr/lib/i386-linux-gnu --disable-vda --enable-libbluray --enable-libcdio --enable-gnutls --enable-frei0r --enable-openssl --enable-libass --enable-libopus --enable-fontconfig --enable-libpulse --disable-mips32r2 --disable-mipsdspr1 --disable-mipsdspr2 --enable-libvidstab --enable-libzvbi --enable-avresample --disable-htmlpages --disable-podpages --enable-libutvideo --enable-libfdk-aac --enable-libx265 --enable-libiec61883 --enable-vaapi --enable-libdc1394 --disable-altivec --shlibdir=/usr/lib/i386-linux-gnu
  
    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 11.102 /  5. 11.102
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  Invalid UE golomb code
  
      Last message repeated 2 times
  
  Input #0, mpegts, from 'http://source.com/1.ts':
  
    Duration: N/A, start: 30472.768167, bitrate: N/A
  
    Program 1
  
      Metadata:
  
        service_name    : Service01
  
        service_provider: FFmpeg
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 960x540 (960x544) [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
  
      Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 105 kb/s
  
  [graph 0 input from stream 0:1 @ 0x971f2c0] tb:1/48000 samplefmt:fltp samplerate:48000 chlayout:0x3
  
  [audio format for output stream 0:0 @ 0x9844de0] auto-inserting filter 'auto-inserted resampler 0' between the filter 'Parsed_anull_0' and the filter 'audio format for output stream 0:0'
  
  [auto-inserted resampler 0 @ 0x97115e0] ch:2 chl:stereo fmt:fltp r:48000Hz -> ch:1 chl:mono fmt:fltp r:22050Hz
  
  [graph 1 input from stream 0:0 @ 0x96f5d00] w:960 h:540 pixfmt:yuv420p tb:1/90000 fr:50/1 sar:1/1 sws_param:flags=2
  
  [scaler for output stream 0:1 @ 0x96f5e80] w:352 h:240 flags:'0x4' interl:0
  
  [scaler for output stream 0:1 @ 0x96f5e80] w:960 h:540 fmt:yuv420p sar:1/1 -> w:352 h:240 fmt:yuv420p sar:40/33 flags:0x4
  
  Output #0, ffm, to 'http://127.0.0.1:8090/feed1.ffm':
  
    Metadata:
  
      creation_time   : now
  
      encoder         : Lavf56.25.101
  
      Stream #0:0: Audio: wmav2, 22050 Hz, mono, fltp, 64 kb/s
  
      Metadata:
  
        encoder         : Lavc56.26.100 wmav2
  
      Stream #0:1: Video: msmpeg4v3 (msmpeg4), yuv420p, 352x240 [SAR 40:33 DAR 16:9], q=2-31, 256 kb/s, 50 fps, 1000k tbn, 15 tbc
  
      Metadata:
  
        encoder         : Lavc56.26.100 msmpeg4
  
  Stream mapping:
  
    Stream #0:1 -> #0:0 (aac (native) -> wmav2 (native))
  
    Stream #0:0 -> #0:1 (h264 (native) -> msmpeg4v3 (msmpeg4))
  
  Press [q] to stop, [?] for help
  
  Invalid UE golomb code
  
  *** dropping frame 3 from stream 1 at ts 1
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x970f060] warning, clipping 1 dct coefficients to -127..127
  
  *** dropping frame 4 from stream 1 at ts 2
  
      Last message repeated 1 times
  
  *** dropping frame 5 from stream 1 at ts 3
  
      Last message repeated 1 times
  
  *** dropping frame 5 from stream 1 at ts 4
  
  *** dropping frame 6 from stream 1 at ts 4
  
      Last message repeated 1 times
  
  *** dropping frame 7 from stream 1 at ts 5
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x970f060] warning, clipping 1 dct coefficients to -127..127
  
  *** dropping frame 8 from stream 1 at ts 6
  
      Last message repeated 1 times
  
  *** dropping frame 8 from stream 1 at ts 7
  
  *** dropping frame 9 from stream 1 at ts 7
  
      Last message repeated 1 times
  
  *** dropping frame 10 from stream 1 at ts 8
  
      Last message repeated 1 times
  
  *** dropping frame 11 from stream 1 at ts 9
  
      Last message repeated 1 times
  
  *** dropping frame 11 from stream 1 at ts 10
  
  *** dropping frame 12 from stream 1 at ts 10
  
      Last message repeated 1 times
  
  *** dropping frame 13 from stream 1 at ts 11
  
      Last message repeated 1 times
  
  *** dropping frame 14 from stream 1 at ts 12
  
      Last message repeated 1 times
  
  *** dropping frame 14 from stream 1 at ts 13
  
  *** dropping frame 15 from stream 1 at ts 13
  
      Last message repeated 1 times
  
  *** dropping frame 16 from stream 1 at ts 14
  
      Last message repeated 1 times
  
  *** dropping frame 17 from stream 1 at ts 15
  
      Last message repeated 1 times
  
  *** dropping frame 17 from stream 1 at ts 16
  
  *** dropping frame 18 from stream 1 at ts 16
  
      Last message repeated 1 times
  
  *** dropping frame 19 from stream 1 at ts 17
  
      Last message repeated 1 times
  
  *** dropping frame 20 from stream 1 at ts 18me=00:00:01.33 bitrate= 270.3kbits/s dup=0 drop=39
  
      Last message repeated 1 times
  
  *** dropping frame 20 from stream 1 at ts 19
  
  *** dropping frame 21 from stream 1 at ts 19
  
      Last message repeated 1 times
  
  *** dropping frame 22 from stream 1 at ts 20
  
      Last message repeated 1 times
  
  *** dropping frame 23 from stream 1 at ts 21
  
      Last message repeated 1 times
  
  *** dropping frame 23 from stream 1 at ts 22
  
  *** dropping frame 24 from stream 1 at ts 22
  
      Last message repeated 1 times
  
  *** dropping frame 25 from stream 1 at ts 23
  
      Last message repeated 1 times
  
  *** dropping frame 26 from stream 1 at ts 24
  
      Last message repeated 1 times
  
  *** dropping frame 26 from stream 1 at ts 25
  
  *** dropping frame 27 from stream 1 at ts 25
  
      Last message repeated 1 times
  
  *** dropping frame 28 from stream 1 at ts 26
  
      Last message repeated 1 times
  
  *** dropping frame 29 from stream 1 at ts 27
  
      Last message repeated 1 times
  
  *** dropping frame 29 from stream 1 at ts 28
  
  *** dropping frame 30 from stream 1 at ts 28
  
      Last message repeated 1 times
  
  *** dropping frame 31 from stream 1 at ts 29
  
      Last message repeated 1 times
  
  *** dropping frame 32 from stream 1 at ts 30
  
      Last message repeated 1 times
  
  *** dropping frame 32 from stream 1 at ts 31
  
  *** dropping frame 33 from stream 1 at ts 31
  
      Last message repeated 1 times
  
  *** dropping frame 34 from stream 1 at ts 32
  
      Last message repeated 1 times
  
  *** dropping frame 34 from stream 1 at ts 33
  
  *** dropping frame 35 from stream 1 at ts 33
  
  *** dropping frame 35 from stream 1 at ts 34
  
  *** dropping frame 36 from stream 1 at ts 34
  
      Last message repeated 1 times
  
  *** dropping frame 37 from stream 1 at ts 35
  
      Last message repeated 1 times
  
  Invalid UE golomb code
  
  *** dropping frame 38 from stream 1 at ts 36
  
      Last message repeated 1 times
  
  *** dropping frame 38 from stream 1 at ts 37
  
  *** dropping frame 39 from stream 1 at ts 37
  
      Last message repeated 1 times
  
  *** dropping frame 40 from stream 1 at ts 38
  
      Last message repeated 1 times
  
  *** dropping frame 41 from stream 1 at ts 39me=00:00:02.73 bitrate= 311.7kbits/s dup=0 drop=88
  
      Last message repeated 1 times
  
  *** dropping frame 41 from stream 1 at ts 40
  
  *** dropping frame 42 from stream 1 at ts 40
  
      Last message repeated 1 times
  
  *** dropping frame 43 from stream 1 at ts 41
  
      Last message repeated 1 times
  
  *** dropping frame 44 from stream 1 at ts 42
  
      Last message repeated 1 times
  
  *** dropping frame 44 from stream 1 at ts 43
  
  *** dropping frame 45 from stream 1 at ts 43
  
      Last message repeated 1 times
  
  *** dropping frame 46 from stream 1 at ts 44
  
      Last message repeated 1 times
  
  *** dropping frame 47 from stream 1 at ts 45
  
      Last message repeated 1 times
  
  *** dropping frame 47 from stream 1 at ts 46
  
  *** dropping frame 48 from stream 1 at ts 46
  
      Last message repeated 1 times
  
  *** dropping frame 49 from stream 1 at ts 47
  
      Last message repeated 1 times
  
  *** dropping frame 50 from stream 1 at ts 48
  
      Last message repeated 1 times
  
  *** dropping frame 50 from stream 1 at ts 49
  
  *** dropping frame 51 from stream 1 at ts 49
  
      Last message repeated 1 times
  
  *** dropping frame 52 from stream 1 at ts 50
  
      Last message repeated 1 times
  
  *** dropping frame 53 from stream 1 at ts 51
  
      Last message repeated 1 times
  
  [h264 @ 0x9844a00] error while decoding MB 58 12, bytestream -5
  
  [h264 @ 0x9844a00] concealing 1311 DC, 1311 AC, 1311 MV errors in B frame
  
  *** dropping frame 53 from stream 1 at ts 52
  
  No more output streams to write to, finishing.
  
  frame=   55 fps= 42 q=4.3 Lsize=     152kB time=00:00:03.66 bitrate= 339.6kbits/s dup=0 drop=119
  
  video:116kB audio:26kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 6.760316%
  
  Input file #0 (http://source.com/1.ts):
  
    Input stream #0:0 (video): 174 packets read (220322 bytes); 174 frames decoded;
  
    Input stream #0:1 (audio): 156 packets read (36657 bytes); 156 frames decoded (159744 samples);
  
    Total: 330 packets (256979 bytes) demuxed
  
  Output file #0 (http://127.0.0.1:8090/feed1.ffm):
  
    Output stream #0:0 (audio): 72 frames encoded (73383 samples); 72 packets muxed (26712 bytes);
  
    Output stream #0:1 (video): 55 frames encoded; 55 packets muxed (119080 bytes);
  
    Total: 127 packets (145792 bytes) muxed

  Here input url file info After i download it to my PC with IDM

  General
  
  ID                             : 1 (0x1)
  
  Complete name                  : D:\1.ts
  
  Format                         : MPEG-TS
  
  File size                      : 256 KiB
  
  Duration                       : 2 s 520 ms
  
  Overall bit rate mode          : Variable
  
  Overall bit rate               : 788 kb/s
  
  
  
  Video
  
  ID                             : 256 (0x100)
  
  Menu ID                        : 1 (0x1)
  
  Format                         : AVC
  
  Format/Info                    : Advanced Video Codec
  
  Format profile                 : High@L3.1
  
  Format settings, CABAC         : Yes
  
  Format settings, RefFrames     : 2 frames
  
  Codec ID                       : 27
  
  Duration                       : 2 s 680 ms
  
  Width                          : 960 pixels
  
  Height                         : 540 pixels
  
  Display aspect ratio           : 16:9
  
  Frame rate                     : 50.000 FPS
  
  Color space                    : YUV
  
  Chroma subsampling             : 4:2:0
  
  Bit depth                      : 8 bits
  
  Scan type                      : Progressive
  
  
  
  Audio
  
  ID                             : 257 (0x101)
  
  Menu ID                        : 1 (0x1)
  
  Format                         : AAC
  
  Format/Info                    : Advanced Audio Codec
  
  Format version                 : Version 4
  
  Format profile                 : LC
  
  Muxing mode                    : ADTS
  
  Codec ID                       : 15
  
  Duration                       : 2 s 69 ms
  
  Bit rate mode                  : Variable
  
  Channel(s)                     : 2 channels
  
  Channel positions              : Front: L R
  
  Sampling rate                  : 48.0 kHz
  
  Frame rate                     : 46.875 FPS (1024 SPF)
  
  Compression mode               : Lossy
  
  Delay relative to video        : -12 ms
  
  
  
  Menu
  
  ID                             : 4096 (0x1000)
  
  Menu ID                        : 1 (0x1)
  
  Duration                       : 2 s 520 ms
  
  List                           : 256 (0x100) (AVC) / 257 (0x101) (AAC)
  
  Service name                   : Service01
  
  Service provider               : FFmpeg
  
  Service type                   : digital television

• Open Banking Security 101 : Is open banking safe ?

  3 décembre 2024, par Daniel Crough — Banking and Financial Services

  Open banking is changing the financial industry. Statista reports that open banking transactions hit $57 billion worldwide in 2023 and will likely reach $330 billion by 2027. According to ACI, global real-time payment (RTP) transactions are expected to exceed $575 billion by 2028.

  Open banking is changing how banking works, but is it safe ? And what are the data privacy and security implications for global financial service providers ?

  This post explains the essentials of open banking security and addresses critical data protection and compliance questions. We’ll explore how a privacy-first approach to data analytics can help you meet regulatory requirements, build customer trust and ultimately thrive in the open banking market while offering innovative financial products.

   

  

  

  EU Financial Services Analytics Maturity Report

  Discover trends, strategies, and opportunities to balance compliance and competitiveness.

  Download the report now

  What is open banking ?

  Open banking is a system that connects banks, authorised third-party providers and technology, empowering customers to securely share their financial data with other companies. At the same time, it unlocks access to more innovative and personalised financial products and services like spend management solutions, tailored budgeting apps and more convenient payment gateways. 

  With open banking, consumers have greater choice and control over their financial data, ultimately fostering a more competitive financial industry, supporting technological innovation and paving the way for a more customer-centric financial future.

  Imagine offering your clients a service that analyses spending habits across all accounts — no matter the institution — and automatically finds ways to save them money. Envision providing personalised financial advice tailored to individual needs or enabling customers to apply for a mortgage with just a few taps on their phone. That’s the power of open banking.

  Embracing this technology is an opportunity for banks and fintech companies to build new solutions for customers who are eager for a more transparent and personalised digital experience.

  How is open banking different from traditional banking ?

  In traditional banking, consumers’ financial data is locked away and siloed within each bank’s systems, accessible only to the bank and the account holder. While account holders could manually aggregate and share this data, the process is cumbersome and prone to errors.

  With open banking, users can choose what data to share and with whom, allowing trusted third-party providers to access their financial information directly from the source. 

  

  How does open banking work ?

  The technology that makes open banking possible is the application programming interface (API). Think of banking APIs as digital translators for different software systems ; instead of translating languages, they translate data and code.

  The bank creates and publishes APIs that provide secure access to specific types of customer data, like credit card transaction history and account balances. The open banking API acts like a friendly librarian, ready to assist apps in accessing the information they need in a secure and organised way.

  Third-party providers, like fintech companies, use these APIs to build their applications and services. Some tech companies also act as intermediaries between fintechs and banks to simplify connections to multiple APIs simultaneously.

  For example, banks like BBVA (Spain) and Capital One (USA) offer secure API platforms. Fintechs like Plaid and TrueLayer use those banking APIs as a bridge to users’ financial data. This bridge gives other service providers like Venmo, Robinhood and Coinbase access to customer data, allowing them to offer new payment gateways and investment tools that traditional banks don’t provide.

  Is open banking safe for global financial services ?

  Yes, open banking is designed from the ground up to be safe for global financial services.

  Open banking doesn’t make customer financial data publicly available. Instead, it uses a secure, regulated framework for sharing information. This framework relies on strong security measures and regulatory oversight to protect user data and ensure responsible access by authorised third-party providers.

  In the following sections, we’ll explore the key security features and banking regulations that make this technology safe and reliable.

  Regulatory compliance in open banking

  Regulatory oversight is a cornerstone of open banking security.

  In the UK and the EU, strict regulations govern how companies access and use customer data. The revised Payment Services Directive (PSD2) in Europe mandates strong customer authentication and secure communication, promoting a high level of security for open banking services.

  To offer open banking services, companies must register with their respective regulatory bodies and comply with all applicable data protection laws.

  For example, third-party service providers in the UK must be authorised by the Financial Conduct Authority (FCA) and listed on the Financial Services Register. Depending on the service they provide, they must get an Account Information Service Provider (AISP) or a Payment Initiation Service Provider (PISP) license.

  Similar regulations and registries exist across Europe, enforced by the European National Competent Authority, like BaFin in Germany and the ACPR in France.

  In the United States, open banking providers don’t require a special federal license. However, this will soon change, as the U.S. Consumer Financial Protection Bureau (CFPB) unveiled a series of rules on 22 October 2024 to establish a regulatory framework for open banking.

  These regulations ensure that only trusted providers can participate in the open banking ecosystem. Anyone can check if a company is a trusted provider on public databases like the Regulated Providers registry on openbanking.org.uk. While being registered doesn’t guarantee fair play, it adds a layer of safety for consumers and banks.

  Key open banking security features that make it safe for global financial services

  Open banking is built on a foundation of solid security measures. Let’s explore five key features that make it safe and reliable for financial institutions and their customers.

  

  Strong Customer Authentication (SCA)

  Strong Customer Authentication (SCA) is a security principle that protects against unauthorised access to user financial data. It’s a regulated and legally required form of multi-factor authentication (MFA) within the European Economic Area.

  SCA mandates that users verify their identity using at least two of the following three factors :

  • Something they know (a password, PIN, security question, etc.)
  • Something they have (a mobile phone, a hardware token or a bank card)
  • Something they are (a fingerprint, facial recognition or voice recognition)

  This type of authentication helps reduce the risk of fraud and unauthorised transactions.

  API security

  PSD2 regulations mandate that banks provide open APIs, giving consumers the right to use any third-party service provider for their online banking services. According to McKinsey research, this has led to a surge in API adoption within the banking sector, with the largest banks allocating 14% of their IT budget to APIs. 

  To ensure API security, banks and financial service providers implement several measures, including :

  • API gateways, which act as a central point of control for all API traffic, enforcing security policies and preventing unauthorised access
  • API keys and tokens to authenticate and authorise API requests (the equivalent of a library card for apps)
  • Rate limiting to prevent denial-of-service attacks by limiting the number of requests a third-party application can make within a specific timeframe
  • Regular security audits and penetration testing to identify and address potential vulnerabilities in the API infrastructure

  Data minimisation and purpose limitation

  Data minimisation and purpose limitation are fundamental principles of data protection that contribute significantly to open banking safety.

  Data minimisation means third parties will collect and process only the data necessary to provide their service. Purpose limitation requires them to use the collected data only for its original purpose.

  For example, a budgeting app that helps users track their spending only needs access to transaction history and account balances. It doesn’t need access to the user’s full transaction details, investment portfolio or loan applications.

  Limiting the data collected from individual banks significantly reduces the risk of potential misuse or exposure in a data breach.

  Encryption

  Encryption is a security method that protects data in transit and at rest. It scrambles data into an unreadable format, making it useless to anyone without the decryption key.

  In open banking, encryption protects users’ data as it travels between the bank and the third-party provider’s systems via the API. It also protects data stored on the bank’s and the provider’s servers. Encryption ensures that even if a breach occurs, user data remains confidential.

  Explicit consent

  In open banking, before a third-party provider can access user data, it must first inform the user what data it will pull and why. The customer must then give their explicit consent to the third party collecting and processing that data.

  This transparency and control are essential for building trust and ensuring customers feel safe using third-party services.

  But beyond that, from the bank’s perspective, explicit customer consent is also vital for compliance with GDPR and other data protection regulations. It can also help limit the bank’s liability in case of a data breach.

  Explicit consent goes beyond sharing financial data. It’s also part of new data privacy regulations around tracking user behaviour online. This is where an ethical web analytics solution like Matomo can be invaluable. Matomo fully complies with some of the world’s strictest privacy regulations, like GDPR, lGPD and HIPAA. With Matomo, you get peace of mind knowing you can continue gathering valuable insights to improve your services and user experience while respecting user privacy and adhering to regulations.

  Risks of open banking for global financial services

  While open banking offers significant benefits, it’s crucial to acknowledge the associated risks. Understanding these risks allows financial institutions to implement safeguards and protect themselves and their customers.

  

  Risk of data breaches

  By its nature, open banking is like adding more doors and windows to your house. It’s convenient but also gives burglars more ways to break in.

  Open banking increases what cybersecurity professionals call the “attack surface,” or the number of potential points of vulnerability for hackers to steal financial data.

  Data breaches are a serious threat to banks and financial institutions. According to IBM’s 2024 Cost of a Data Breach Report, each breach costs companies in the US an average of $4.88 million. Therefore, banks and fintechs must prioritise strong security measures and data protection protocols to mitigate these risks.

  Risk of third-party access

  By definition, open banking involves granting third-party providers access to customer financial information. This introduces a level of risk outside the bank’s direct control.

  Financial institutions must carefully vet third-party providers, ensuring they meet stringent security standards and comply with all relevant data protection regulations.

  Risk of user account takeover

  Open banking can increase the risk of user account takeover if adequate security measures are not in place. For example, if a malicious third-party provider gains unauthorised access to a user’s bank login details, they could take control of the user’s account and make fraudulent bank transactions.

  A proactive approach to security, continuous monitoring and a commitment to evolving best practices and security protocols are crucial for navigating the open banking landscape.

  Open banking and data analytics : A balancing act for financial institutions

  The additional data exchanged through open banking unveils deeper insights into customer behaviour and preferences. This data can fuel innovation, enabling the development of personalised products and services and improved risk management strategies.

  However, using this data responsibly requires a careful balancing act.

  Too much reliance on data without proper safeguards can erode trust and invite regulatory issues. The opposite can stifle innovation and limit the technology’s potential.

  Matomo Analytics derisks web and app environments by giving full control over what data is tracked and how it is stored. The platform prioritises user data privacy and security while providing valuable data and analytics that will be familiar to anyone who has used Google Analytics.

  Open banking, data privacy and AI

  The future of open banking is entangled with emerging technologies like artificial intelligence (AI) and machine learning. These technologies significantly enhance open banking analytics, personalise services, and automate financial tasks.

  Several banks, credit unions and financial service providers are already exploring AI’s potential in open banking. For example, HSBC developed the AI-enabled FX Prompt in 2023 to improve forex trading. The bank processed 823 million client API calls, many of which were open banking.

  However, using AI in open banking raises important data privacy considerations. As the American Bar Association highlights, balancing personalisation with responsible AI use is crucial for open banking’s future. Financial institutions must ensure that AI-driven solutions are developed and implemented ethically, respecting customer privacy and data protection.

  Conclusion

  Open banking presents a significant opportunity for innovation and growth in the financial services industry. While it’s important to acknowledge the associated risks, security measures like explicit customer consent, encryption and regulatory frameworks make open banking a safe and reliable system for banks and their clients.

  Financial service providers must adopt a multifaceted approach to data privacy, implementing privacy-centred solutions across all aspects of their business, from open banking to online services and web analytics.

  By prioritising data privacy and security, financial institutions can build customer trust, unlock the full potential of open banking and thrive in today’s changing financial environment.

• How to not process any personal data with Matomo and what it means for you

  22 avril 2018, par InnoCraft

  Disclaimer : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to explain how to not process any personal data with Matomo in order to avoid going through the GDPR compliance process with Matomo analytics. This work comes from our interpretation of different sources : the official GDPR text and the UK privacy commission : ICO resources. It cannot be considered as a professional legal advice. So as GDPR, this information is subject to change. GDPR may be also known as RGPD in French, Spanish, Portuguese, Datenschutz-Grundverordnung, DS-GVO in German, Algemene verordening gegevensbescherming in Dutch, Regolamento generale sulla protezione dei dati in Italian.

  Are you looking for a way to not process any personal data with Matomo ? If the answer is yes, you are at the right place. From our understanding, if you are not processing personal data, then you shouldn’t be concerned about GDPR. Our inspiration came from this official reference :

  “The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. This Regulation does not therefore concern the processing of such anonymous information, including for statistical or research purposes.“

  In this blog post we are going to see how you can configure Matomo in order to not process any personal data and what the consequences are.

  Which data is considered as personal according to GDPR ?

  From : eur-lex.europa.eu

  (1) “‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’) ; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person ;”

  (30) “Natural persons may be associated with online identifiers provided by their devices, applications, tools and protocols, such as internet protocol addresses, cookie identifiers or other identifiers such as radio frequency identification tags. This may leave traces which, in particular when combined with unique identifiers and other information received by the servers, may be used to create profiles of the natural persons and identify them.”

  So according to your Matomo configuration, it may leave some traces within the following data :

  1. IP addresses
  2. Cookies identifiers
  3. Page URL or page titles
  4. User ID and Custom “personal” data
  5. Ecommerce order IDs
  6. Location
  7. Heatmaps & Session Recordings

  Let’s see each of them in more detail.

  1. IP addresses

  IP addresses can indirectly identify an individual. It can also give a good approximation of an individual’s location.

  IP addresses are therefore considered as personal data which means you need to anonymize them. To do so, a feature is available within Matomo, where you can anonymize the IP. We recommend you to anonymize at least the last two bytes :

  

  See our configuration guide for more information

  What are the consequences of using this feature ?

  When applying IP anonymization on two bytes, you will no longer be able to see the full IP in the UI.

  Moreover, there is a small chance that 2 different visitors with the same device and software configuration will be identified as the same visitor if the anonymised IP address is the same for both.

  2. Cookies

  It is not clear for us yet if all cookies are considered equal under GDPR. At this stage it is too early to make a definite decision.

  Did you know ? Matomo lets you optionally disable the creation of cookies by adding an extra line of code to your tracking code see below.

  

  See our configuration guide for more information

  What are the consequences of using this feature ?

  Matomo is using a few first party cookies, and the following cookies may hold personal data :

  • _pk_id : contains a visitor id used to identify unique visitors
  • _pk_ref : to identify from where they came from

  If Matomo cannot set cookies, it will use a technique called Fingerprint. It is based on several metadata such as the operating system, browser, browser plugins, IP address, browser language ; just to name a few to identify a unique visitor. As this feature is less accurate than the one using cookies, the number of visitors and visits will be affected.

  3. Page URLs and page titles

  URLs are not mentioned within the official GDPR text. However, we know that according to the different CMS you use, some of them may have URLs including personal identifiers.

  For example :

  

  As a result, you need to find a way to anonymize this data.

  There are several ways you can perform this action according to your website. If your website is adding the personal data through query parameters, you can define a rule to exclude them from Matomo.

  If the personal data are not included within query parameters, you can use the “setCustomURL” feature and write your code as follow :

  

  See our developer documentation for more information

  If you are also processing personal data within the title tag, you can use the following function : “setDocumentTitle”.

  What are the consequences of using this feature ?

  By anonymizing the URLs containing personal data, some of your  URLs will be grouped together.

  4. User ID and custom personal data

  User ID is a feature (a tracking code needs to be added) which allows you to identify the same user across different devices.

  A User ID needs a corresponding database in order to link a user across different devices, it can be an email, a username, a name, a random number… All those data are either direct or non direct online identifiers and are therefore under the scope of GDPR.

  It will be the same situation if you are using custom variables and/or custom dimensions in order to push personal data to the system.

  To continue using the User ID feature but not recording personal data, you can consider using a hash function which will anonymize/convert your actual User ID into something like “3jrj3j34434834urj33j3”.

  Alternatively, you can enable the feature “Anonymise User IDs”. This feature will be available starting in Matomo 3.5.0 :

  

  What are the consequences of using this feature ?

  Under GDPR, User ID is personal data. Anonymizing the User ID using a hash function or our built-in functionality make the User Id pseudo-anonymous, which means it can’t be easily identified to a specific user. As a result, you will still get accurate visits and unique visitors metrics, and the Visitor Profile, but without tracking the original User ID which is personal data.

  5. Ecommerce order IDs

  Order IDs are the reference number assigned to the products/services bought by your customers. As this information can be crossed with your internal database, it is considered as an online identifier and is therefore under the scope of GDPR. As for User ID, you can anonymize order IDs using our built-in functionality to Anonymise Order IDs (see section 4. about User Id).

  What are the consequences of anonymizing order ID ?

  It really depends on your former use of order IDs. If you were not using them in the past then you should not see any difference.

  6. Location

  Based on the IP address of a visitor, Matomo can detect the visitors location. Location data is problematic for privacy as this technology has become quite accurate and can detect not only the city a visitor is from, but sometimes an even more precise position of a visitor.

  

  In order to not leave any accurate traces, we strongly recommend you to enable the IP anonymization feature. Next, you need to enable the setting “Also use the anonymized IP address when enriching visits”. You find this setting directly below the IP anonymization. This is important as otherwise the full IP address will be used to geolocate a visitor.

  

  What are the consequences of anonymizing location data ?

  The more bytes you anonymize from the IP, the more anonymized your location will be. When you remove two bytes as suggested, the city and region location reports will not be as accurate. In some cases even the country may not be detected correctly anymore.

  7. Heatmaps & Session Recordings

  Heatmaps & Session Recording is a premium feature in Matomo allowing you to see where users click, hover, type and scroll. With session recordings you can then replay their actions in a video.

  Heatmaps & Session Recordings are under the scope of GDPR as they can disclose in some specific cases (for example : filling a contact form) personal data :

  

  To avoid this, Matomo will anonymize all keystrokes which a user enters into a form field unless you specifically whitelist a field. Many fields that could contain personal data, such as a credit card, phone number, email address, password, social security number, and more are always anonymized and not recorded.

  See our configuration guide for more information

  Note that a page may still show personal information within the page as part of regular content (not a form element). For example an address, or the profile page of a forum user. We have added a feature which allows you to set an HTML attribute “data-matomo-mask” to anonymize any personal content shown in the UI.

  What are the consequences of using this feature ?

  Mainly, you will not be able to see in plain text what people are entering into your forms.

  What should you do with past data ?

  Once more, we have to say that we are not lawyers. So do not take our answers as legal advice. From : ec.europa.eu/newsroom/article29/document.cfm ?doc_id=50053

  “For example, as the GDPR requires that a controller must be able to demonstrate that valid consent was obtained, all presumed consents of which no references are kept will automatically be below the consent standard of the GDPR and will need to be renewed.”

  Our interpretation is that, if you were previously relying on consent, unless you can demonstrate that valid consent was obtained, you need to get the consent back (which is almost impossible) or you need to anonymize or remove that data.

  To anonymize previously tracked data, we are actively working on a feature to do just that directly within Matomo. Alternatively, you may also set up the deletion of logs after a certain amount of time.

  We really hope you enjoyed reading this article. GDPR is still on the go and we are pretty sure you have a lot of questions about it. You probably would like to share our vision about it. So do not hesitate to ask us through our contact form to see how we are interpreting GDPR at Matomo and InnoCraft.

  The post How to not process any personal data with Matomo and what it means for you appeared first on Analytics Platform - Matomo.